published on Tuesday, Apr 21, 2026 by Pulumi
published on Tuesday, Apr 21, 2026 by Pulumi
Resource for creating chaos experiments from experiment templates.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as harness from "@pulumi/harness";
// ============================================================================
// Harness Chaos Experiment Resource Examples
// ============================================================================
//
// Chaos Experiments are INSTANCES created FROM Experiment Templates.
// These examples are based on TESTED configurations from the e2e-test suite.
//
// Key Points:
// - Experiments are created by "launching" an experiment template
// - Infrastructure binding (infra_ref) is MANDATORY (format: env_id/infra_id)
// - Hub scope can be different from experiment scope (cross-scope support)
// - import_type: "REFERENCE" (default) or "LOCAL" (full copy)
// ============================================================================
// ----------------------------------------------------------------------------
// Example 1: Basic Experiment with REFERENCE Import
// ----------------------------------------------------------------------------
// Most common pattern: project-level experiment from project-level template
const basic = new harness.chaos.Experiment("basic", {
orgId: "my_org",
projectId: "my_project",
hubOrgId: "my_org",
hubProjectId: "my_project",
hubIdentity: "my-chaos-hub",
templateIdentity: "my-template",
infraRef: "my-env/my-infra",
name: "My Chaos Experiment",
identity: "my-chaos-experiment",
description: "Basic chaos experiment with REFERENCE import",
importType: "REFERENCE",
tags: [
"chaos",
"kubernetes",
"resilience",
],
}, {
dependsOn: [
myTemplate,
myInfra,
],
});
// ----------------------------------------------------------------------------
// Example 2: Experiment with LOCAL Import
// ----------------------------------------------------------------------------
// LOCAL import creates a full copy - independent of template changes
const localCopy = new harness.chaos.Experiment("local_copy", {
orgId: "my_org",
projectId: "my_project",
hubOrgId: "my_org",
hubProjectId: "my_project",
hubIdentity: "my-chaos-hub",
templateIdentity: "my-template",
infraRef: "my-env/my-infra",
name: "My Independent Experiment",
identity: "my-independent-experiment",
description: "Experiment with LOCAL import (independent copy)",
importType: "LOCAL",
tags: [
"chaos",
"local",
"independent",
],
}, {
dependsOn: [
myTemplate,
myInfra,
],
});
// ----------------------------------------------------------------------------
// Example 3: Cross-Scope Experiment (Org Hub → Project Experiment)
// ----------------------------------------------------------------------------
// Create project experiment from org-level template (cross-scope)
const crossScope = new harness.chaos.Experiment("cross_scope", {
orgId: "my_org",
projectId: "my_project",
hubOrgId: "my_org",
hubIdentity: "my-chaos-hub",
templateIdentity: "my-template",
infraRef: "my-env/my-infra",
name: "Cross-Scope Experiment",
identity: "cross-scope-experiment",
description: "Project experiment from org-level template",
importType: "REFERENCE",
tags: [
"chaos",
"cross-scope",
"org-template",
],
}, {
dependsOn: [
orgTemplate,
myInfra,
],
});
import pulumi
import pulumi_harness as harness
# ============================================================================
# Harness Chaos Experiment Resource Examples
# ============================================================================
#
# Chaos Experiments are INSTANCES created FROM Experiment Templates.
# These examples are based on TESTED configurations from the e2e-test suite.
#
# Key Points:
# - Experiments are created by "launching" an experiment template
# - Infrastructure binding (infra_ref) is MANDATORY (format: env_id/infra_id)
# - Hub scope can be different from experiment scope (cross-scope support)
# - import_type: "REFERENCE" (default) or "LOCAL" (full copy)
# ============================================================================
# ----------------------------------------------------------------------------
# Example 1: Basic Experiment with REFERENCE Import
# ----------------------------------------------------------------------------
# Most common pattern: project-level experiment from project-level template
basic = harness.chaos.Experiment("basic",
org_id="my_org",
project_id="my_project",
hub_org_id="my_org",
hub_project_id="my_project",
hub_identity="my-chaos-hub",
template_identity="my-template",
infra_ref="my-env/my-infra",
name="My Chaos Experiment",
identity="my-chaos-experiment",
description="Basic chaos experiment with REFERENCE import",
import_type="REFERENCE",
tags=[
"chaos",
"kubernetes",
"resilience",
],
opts = pulumi.ResourceOptions(depends_on=[
my_template,
my_infra,
]))
# ----------------------------------------------------------------------------
# Example 2: Experiment with LOCAL Import
# ----------------------------------------------------------------------------
# LOCAL import creates a full copy - independent of template changes
local_copy = harness.chaos.Experiment("local_copy",
org_id="my_org",
project_id="my_project",
hub_org_id="my_org",
hub_project_id="my_project",
hub_identity="my-chaos-hub",
template_identity="my-template",
infra_ref="my-env/my-infra",
name="My Independent Experiment",
identity="my-independent-experiment",
description="Experiment with LOCAL import (independent copy)",
import_type="LOCAL",
tags=[
"chaos",
"local",
"independent",
],
opts = pulumi.ResourceOptions(depends_on=[
my_template,
my_infra,
]))
# ----------------------------------------------------------------------------
# Example 3: Cross-Scope Experiment (Org Hub → Project Experiment)
# ----------------------------------------------------------------------------
# Create project experiment from org-level template (cross-scope)
cross_scope = harness.chaos.Experiment("cross_scope",
org_id="my_org",
project_id="my_project",
hub_org_id="my_org",
hub_identity="my-chaos-hub",
template_identity="my-template",
infra_ref="my-env/my-infra",
name="Cross-Scope Experiment",
identity="cross-scope-experiment",
description="Project experiment from org-level template",
import_type="REFERENCE",
tags=[
"chaos",
"cross-scope",
"org-template",
],
opts = pulumi.ResourceOptions(depends_on=[
org_template,
my_infra,
]))
package main
import (
"github.com/pulumi/pulumi-harness/sdk/go/harness/chaos"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
// ============================================================================
// Harness Chaos Experiment Resource Examples
// ============================================================================
//
// Chaos Experiments are INSTANCES created FROM Experiment Templates.
// These examples are based on TESTED configurations from the e2e-test suite.
//
// Key Points:
// - Experiments are created by "launching" an experiment template
// - Infrastructure binding (infra_ref) is MANDATORY (format: env_id/infra_id)
// - Hub scope can be different from experiment scope (cross-scope support)
// - import_type: "REFERENCE" (default) or "LOCAL" (full copy)
// ============================================================================
// ----------------------------------------------------------------------------
// Example 1: Basic Experiment with REFERENCE Import
// ----------------------------------------------------------------------------
// Most common pattern: project-level experiment from project-level template
_, err := chaos.NewExperiment(ctx, "basic", &chaos.ExperimentArgs{
OrgId: pulumi.String("my_org"),
ProjectId: pulumi.String("my_project"),
HubOrgId: pulumi.String("my_org"),
HubProjectId: pulumi.String("my_project"),
HubIdentity: pulumi.String("my-chaos-hub"),
TemplateIdentity: pulumi.String("my-template"),
InfraRef: pulumi.String("my-env/my-infra"),
Name: pulumi.String("My Chaos Experiment"),
Identity: pulumi.String("my-chaos-experiment"),
Description: pulumi.String("Basic chaos experiment with REFERENCE import"),
ImportType: pulumi.String("REFERENCE"),
Tags: pulumi.StringArray{
pulumi.String("chaos"),
pulumi.String("kubernetes"),
pulumi.String("resilience"),
},
}, pulumi.DependsOn([]pulumi.Resource{
myTemplate,
myInfra,
}))
if err != nil {
return err
}
// ----------------------------------------------------------------------------
// Example 2: Experiment with LOCAL Import
// ----------------------------------------------------------------------------
// LOCAL import creates a full copy - independent of template changes
_, err = chaos.NewExperiment(ctx, "local_copy", &chaos.ExperimentArgs{
OrgId: pulumi.String("my_org"),
ProjectId: pulumi.String("my_project"),
HubOrgId: pulumi.String("my_org"),
HubProjectId: pulumi.String("my_project"),
HubIdentity: pulumi.String("my-chaos-hub"),
TemplateIdentity: pulumi.String("my-template"),
InfraRef: pulumi.String("my-env/my-infra"),
Name: pulumi.String("My Independent Experiment"),
Identity: pulumi.String("my-independent-experiment"),
Description: pulumi.String("Experiment with LOCAL import (independent copy)"),
ImportType: pulumi.String("LOCAL"),
Tags: pulumi.StringArray{
pulumi.String("chaos"),
pulumi.String("local"),
pulumi.String("independent"),
},
}, pulumi.DependsOn([]pulumi.Resource{
myTemplate,
myInfra,
}))
if err != nil {
return err
}
// ----------------------------------------------------------------------------
// Example 3: Cross-Scope Experiment (Org Hub → Project Experiment)
// ----------------------------------------------------------------------------
// Create project experiment from org-level template (cross-scope)
_, err = chaos.NewExperiment(ctx, "cross_scope", &chaos.ExperimentArgs{
OrgId: pulumi.String("my_org"),
ProjectId: pulumi.String("my_project"),
HubOrgId: pulumi.String("my_org"),
HubIdentity: pulumi.String("my-chaos-hub"),
TemplateIdentity: pulumi.String("my-template"),
InfraRef: pulumi.String("my-env/my-infra"),
Name: pulumi.String("Cross-Scope Experiment"),
Identity: pulumi.String("cross-scope-experiment"),
Description: pulumi.String("Project experiment from org-level template"),
ImportType: pulumi.String("REFERENCE"),
Tags: pulumi.StringArray{
pulumi.String("chaos"),
pulumi.String("cross-scope"),
pulumi.String("org-template"),
},
}, pulumi.DependsOn([]pulumi.Resource{
orgTemplate,
myInfra,
}))
if err != nil {
return err
}
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Harness = Pulumi.Harness;
return await Deployment.RunAsync(() =>
{
// ============================================================================
// Harness Chaos Experiment Resource Examples
// ============================================================================
//
// Chaos Experiments are INSTANCES created FROM Experiment Templates.
// These examples are based on TESTED configurations from the e2e-test suite.
//
// Key Points:
// - Experiments are created by "launching" an experiment template
// - Infrastructure binding (infra_ref) is MANDATORY (format: env_id/infra_id)
// - Hub scope can be different from experiment scope (cross-scope support)
// - import_type: "REFERENCE" (default) or "LOCAL" (full copy)
// ============================================================================
// ----------------------------------------------------------------------------
// Example 1: Basic Experiment with REFERENCE Import
// ----------------------------------------------------------------------------
// Most common pattern: project-level experiment from project-level template
var basic = new Harness.Chaos.Experiment("basic", new()
{
OrgId = "my_org",
ProjectId = "my_project",
HubOrgId = "my_org",
HubProjectId = "my_project",
HubIdentity = "my-chaos-hub",
TemplateIdentity = "my-template",
InfraRef = "my-env/my-infra",
Name = "My Chaos Experiment",
Identity = "my-chaos-experiment",
Description = "Basic chaos experiment with REFERENCE import",
ImportType = "REFERENCE",
Tags = new[]
{
"chaos",
"kubernetes",
"resilience",
},
}, new CustomResourceOptions
{
DependsOn =
{
myTemplate,
myInfra,
},
});
// ----------------------------------------------------------------------------
// Example 2: Experiment with LOCAL Import
// ----------------------------------------------------------------------------
// LOCAL import creates a full copy - independent of template changes
var localCopy = new Harness.Chaos.Experiment("local_copy", new()
{
OrgId = "my_org",
ProjectId = "my_project",
HubOrgId = "my_org",
HubProjectId = "my_project",
HubIdentity = "my-chaos-hub",
TemplateIdentity = "my-template",
InfraRef = "my-env/my-infra",
Name = "My Independent Experiment",
Identity = "my-independent-experiment",
Description = "Experiment with LOCAL import (independent copy)",
ImportType = "LOCAL",
Tags = new[]
{
"chaos",
"local",
"independent",
},
}, new CustomResourceOptions
{
DependsOn =
{
myTemplate,
myInfra,
},
});
// ----------------------------------------------------------------------------
// Example 3: Cross-Scope Experiment (Org Hub → Project Experiment)
// ----------------------------------------------------------------------------
// Create project experiment from org-level template (cross-scope)
var crossScope = new Harness.Chaos.Experiment("cross_scope", new()
{
OrgId = "my_org",
ProjectId = "my_project",
HubOrgId = "my_org",
HubIdentity = "my-chaos-hub",
TemplateIdentity = "my-template",
InfraRef = "my-env/my-infra",
Name = "Cross-Scope Experiment",
Identity = "cross-scope-experiment",
Description = "Project experiment from org-level template",
ImportType = "REFERENCE",
Tags = new[]
{
"chaos",
"cross-scope",
"org-template",
},
}, new CustomResourceOptions
{
DependsOn =
{
orgTemplate,
myInfra,
},
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.harness.chaos.Experiment;
import com.pulumi.harness.chaos.ExperimentArgs;
import com.pulumi.resources.CustomResourceOptions;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
// ============================================================================
// Harness Chaos Experiment Resource Examples
// ============================================================================
//
// Chaos Experiments are INSTANCES created FROM Experiment Templates.
// These examples are based on TESTED configurations from the e2e-test suite.
//
// Key Points:
// - Experiments are created by "launching" an experiment template
// - Infrastructure binding (infra_ref) is MANDATORY (format: env_id/infra_id)
// - Hub scope can be different from experiment scope (cross-scope support)
// - import_type: "REFERENCE" (default) or "LOCAL" (full copy)
// ============================================================================
// ----------------------------------------------------------------------------
// Example 1: Basic Experiment with REFERENCE Import
// ----------------------------------------------------------------------------
// Most common pattern: project-level experiment from project-level template
var basic = new Experiment("basic", ExperimentArgs.builder()
.orgId("my_org")
.projectId("my_project")
.hubOrgId("my_org")
.hubProjectId("my_project")
.hubIdentity("my-chaos-hub")
.templateIdentity("my-template")
.infraRef("my-env/my-infra")
.name("My Chaos Experiment")
.identity("my-chaos-experiment")
.description("Basic chaos experiment with REFERENCE import")
.importType("REFERENCE")
.tags(
"chaos",
"kubernetes",
"resilience")
.build(), CustomResourceOptions.builder()
.dependsOn(
myTemplate,
myInfra)
.build());
// ----------------------------------------------------------------------------
// Example 2: Experiment with LOCAL Import
// ----------------------------------------------------------------------------
// LOCAL import creates a full copy - independent of template changes
var localCopy = new Experiment("localCopy", ExperimentArgs.builder()
.orgId("my_org")
.projectId("my_project")
.hubOrgId("my_org")
.hubProjectId("my_project")
.hubIdentity("my-chaos-hub")
.templateIdentity("my-template")
.infraRef("my-env/my-infra")
.name("My Independent Experiment")
.identity("my-independent-experiment")
.description("Experiment with LOCAL import (independent copy)")
.importType("LOCAL")
.tags(
"chaos",
"local",
"independent")
.build(), CustomResourceOptions.builder()
.dependsOn(
myTemplate,
myInfra)
.build());
// ----------------------------------------------------------------------------
// Example 3: Cross-Scope Experiment (Org Hub → Project Experiment)
// ----------------------------------------------------------------------------
// Create project experiment from org-level template (cross-scope)
var crossScope = new Experiment("crossScope", ExperimentArgs.builder()
.orgId("my_org")
.projectId("my_project")
.hubOrgId("my_org")
.hubIdentity("my-chaos-hub")
.templateIdentity("my-template")
.infraRef("my-env/my-infra")
.name("Cross-Scope Experiment")
.identity("cross-scope-experiment")
.description("Project experiment from org-level template")
.importType("REFERENCE")
.tags(
"chaos",
"cross-scope",
"org-template")
.build(), CustomResourceOptions.builder()
.dependsOn(
orgTemplate,
myInfra)
.build());
}
}
resources:
# ============================================================================
# Harness Chaos Experiment Resource Examples
# ============================================================================
#
# Chaos Experiments are INSTANCES created FROM Experiment Templates.
# These examples are based on TESTED configurations from the e2e-test suite.
#
# Key Points:
# - Experiments are created by "launching" an experiment template
# - Infrastructure binding (infra_ref) is MANDATORY (format: env_id/infra_id)
# - Hub scope can be different from experiment scope (cross-scope support)
# - import_type: "REFERENCE" (default) or "LOCAL" (full copy)
# ============================================================================
# ----------------------------------------------------------------------------
# Example 1: Basic Experiment with REFERENCE Import
# ----------------------------------------------------------------------------
# Most common pattern: project-level experiment from project-level template
basic:
type: harness:chaos:Experiment
properties:
orgId: my_org
projectId: my_project
hubOrgId: my_org
hubProjectId: my_project
hubIdentity: my-chaos-hub
templateIdentity: my-template
infraRef: my-env/my-infra
name: My Chaos Experiment
identity: my-chaos-experiment
description: Basic chaos experiment with REFERENCE import
importType: REFERENCE
tags:
- chaos
- kubernetes
- resilience
options:
dependsOn:
- ${myTemplate}
- ${myInfra}
# ----------------------------------------------------------------------------
# Example 2: Experiment with LOCAL Import
# ----------------------------------------------------------------------------
# LOCAL import creates a full copy - independent of template changes
localCopy:
type: harness:chaos:Experiment
name: local_copy
properties:
orgId: my_org
projectId: my_project
hubOrgId: my_org
hubProjectId: my_project
hubIdentity: my-chaos-hub
templateIdentity: my-template
infraRef: my-env/my-infra
name: My Independent Experiment
identity: my-independent-experiment
description: Experiment with LOCAL import (independent copy)
importType: LOCAL
tags:
- chaos
- local
- independent
options:
dependsOn:
- ${myTemplate}
- ${myInfra}
# ----------------------------------------------------------------------------
# Example 3: Cross-Scope Experiment (Org Hub → Project Experiment)
# ----------------------------------------------------------------------------
# Create project experiment from org-level template (cross-scope)
crossScope:
type: harness:chaos:Experiment
name: cross_scope
properties:
orgId: my_org
projectId: my_project
hubOrgId: my_org
hubIdentity: my-chaos-hub
templateIdentity: my-template
infraRef: my-env/my-infra
name: Cross-Scope Experiment
identity: cross-scope-experiment
description: Project experiment from org-level template
importType: REFERENCE
tags:
- chaos
- cross-scope
- org-template
options:
dependsOn:
- ${orgTemplate}
- ${myInfra}
Create Experiment Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new Experiment(name: string, args: ExperimentArgs, opts?: CustomResourceOptions);@overload
def Experiment(resource_name: str,
args: ExperimentArgs,
opts: Optional[ResourceOptions] = None)
@overload
def Experiment(resource_name: str,
opts: Optional[ResourceOptions] = None,
project_id: Optional[str] = None,
hub_identity: Optional[str] = None,
infra_ref: Optional[str] = None,
org_id: Optional[str] = None,
template_identity: Optional[str] = None,
hub_org_id: Optional[str] = None,
hub_project_id: Optional[str] = None,
identity: Optional[str] = None,
import_type: Optional[str] = None,
name: Optional[str] = None,
description: Optional[str] = None,
revision: Optional[str] = None,
tags: Optional[Sequence[str]] = None)func NewExperiment(ctx *Context, name string, args ExperimentArgs, opts ...ResourceOption) (*Experiment, error)public Experiment(string name, ExperimentArgs args, CustomResourceOptions? opts = null)
public Experiment(String name, ExperimentArgs args)
public Experiment(String name, ExperimentArgs args, CustomResourceOptions options)
type: harness:chaos:Experiment
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args ExperimentArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args ExperimentArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args ExperimentArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args ExperimentArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args ExperimentArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var experimentResource = new Harness.Chaos.Experiment("experimentResource", new()
{
ProjectId = "string",
HubIdentity = "string",
InfraRef = "string",
OrgId = "string",
TemplateIdentity = "string",
HubOrgId = "string",
HubProjectId = "string",
Identity = "string",
ImportType = "string",
Name = "string",
Description = "string",
Revision = "string",
Tags = new[]
{
"string",
},
});
example, err := chaos.NewExperiment(ctx, "experimentResource", &chaos.ExperimentArgs{
ProjectId: pulumi.String("string"),
HubIdentity: pulumi.String("string"),
InfraRef: pulumi.String("string"),
OrgId: pulumi.String("string"),
TemplateIdentity: pulumi.String("string"),
HubOrgId: pulumi.String("string"),
HubProjectId: pulumi.String("string"),
Identity: pulumi.String("string"),
ImportType: pulumi.String("string"),
Name: pulumi.String("string"),
Description: pulumi.String("string"),
Revision: pulumi.String("string"),
Tags: pulumi.StringArray{
pulumi.String("string"),
},
})
var experimentResource = new Experiment("experimentResource", ExperimentArgs.builder()
.projectId("string")
.hubIdentity("string")
.infraRef("string")
.orgId("string")
.templateIdentity("string")
.hubOrgId("string")
.hubProjectId("string")
.identity("string")
.importType("string")
.name("string")
.description("string")
.revision("string")
.tags("string")
.build());
experiment_resource = harness.chaos.Experiment("experimentResource",
project_id="string",
hub_identity="string",
infra_ref="string",
org_id="string",
template_identity="string",
hub_org_id="string",
hub_project_id="string",
identity="string",
import_type="string",
name="string",
description="string",
revision="string",
tags=["string"])
const experimentResource = new harness.chaos.Experiment("experimentResource", {
projectId: "string",
hubIdentity: "string",
infraRef: "string",
orgId: "string",
templateIdentity: "string",
hubOrgId: "string",
hubProjectId: "string",
identity: "string",
importType: "string",
name: "string",
description: "string",
revision: "string",
tags: ["string"],
});
type: harness:chaos:Experiment
properties:
description: string
hubIdentity: string
hubOrgId: string
hubProjectId: string
identity: string
importType: string
infraRef: string
name: string
orgId: string
projectId: string
revision: string
tags:
- string
templateIdentity: string
Experiment Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The Experiment resource accepts the following input properties:
- Hub
Identity string - Identity of the hub where the experiment template resides. Must include scope prefix for account and org levels: 'account.my-hub' for account-level hubs, 'org.my-hub' for org-level hubs, or just 'my-hub' for project-level hubs (no prefix)
- Infra
Ref string - Infrastructure reference (ID or identity) to bind the experiment to
- Org
Id string - Organization identifier where the experiment will be created
- Project
Id string - Project identifier where the experiment will be created
- Template
Identity string - Identity of the experiment template to launch from
- Description string
- Description of the chaos experiment
- Hub
Org stringId - Organization identifier where the hub/template resides (leave empty for account-level hubs). This is used to locate the template, not where the experiment will be created.
- Hub
Project stringId - Project identifier where the hub/template resides (leave empty for org-level or account-level hubs). This is used to locate the template, not where the experiment will be created.
- Identity string
- Unique identifier for the experiment (auto-generated if not provided)
- Import
Type string - Import type: REFERENCE (template reference) or LOCAL (full copy). Default: REFERENCE
- Name string
- Name of the chaos experiment
- Revision string
- Template revision to use (default: v1)
- List<string>
- Tags to categorize the experiment. Note: Only user-configured tags are tracked in state. The API may add system-generated tags which are automatically filtered to prevent drift.
- Hub
Identity string - Identity of the hub where the experiment template resides. Must include scope prefix for account and org levels: 'account.my-hub' for account-level hubs, 'org.my-hub' for org-level hubs, or just 'my-hub' for project-level hubs (no prefix)
- Infra
Ref string - Infrastructure reference (ID or identity) to bind the experiment to
- Org
Id string - Organization identifier where the experiment will be created
- Project
Id string - Project identifier where the experiment will be created
- Template
Identity string - Identity of the experiment template to launch from
- Description string
- Description of the chaos experiment
- Hub
Org stringId - Organization identifier where the hub/template resides (leave empty for account-level hubs). This is used to locate the template, not where the experiment will be created.
- Hub
Project stringId - Project identifier where the hub/template resides (leave empty for org-level or account-level hubs). This is used to locate the template, not where the experiment will be created.
- Identity string
- Unique identifier for the experiment (auto-generated if not provided)
- Import
Type string - Import type: REFERENCE (template reference) or LOCAL (full copy). Default: REFERENCE
- Name string
- Name of the chaos experiment
- Revision string
- Template revision to use (default: v1)
- []string
- Tags to categorize the experiment. Note: Only user-configured tags are tracked in state. The API may add system-generated tags which are automatically filtered to prevent drift.
- hub
Identity String - Identity of the hub where the experiment template resides. Must include scope prefix for account and org levels: 'account.my-hub' for account-level hubs, 'org.my-hub' for org-level hubs, or just 'my-hub' for project-level hubs (no prefix)
- infra
Ref String - Infrastructure reference (ID or identity) to bind the experiment to
- org
Id String - Organization identifier where the experiment will be created
- project
Id String - Project identifier where the experiment will be created
- template
Identity String - Identity of the experiment template to launch from
- description String
- Description of the chaos experiment
- hub
Org StringId - Organization identifier where the hub/template resides (leave empty for account-level hubs). This is used to locate the template, not where the experiment will be created.
- hub
Project StringId - Project identifier where the hub/template resides (leave empty for org-level or account-level hubs). This is used to locate the template, not where the experiment will be created.
- identity String
- Unique identifier for the experiment (auto-generated if not provided)
- import
Type String - Import type: REFERENCE (template reference) or LOCAL (full copy). Default: REFERENCE
- name String
- Name of the chaos experiment
- revision String
- Template revision to use (default: v1)
- List<String>
- Tags to categorize the experiment. Note: Only user-configured tags are tracked in state. The API may add system-generated tags which are automatically filtered to prevent drift.
- hub
Identity string - Identity of the hub where the experiment template resides. Must include scope prefix for account and org levels: 'account.my-hub' for account-level hubs, 'org.my-hub' for org-level hubs, or just 'my-hub' for project-level hubs (no prefix)
- infra
Ref string - Infrastructure reference (ID or identity) to bind the experiment to
- org
Id string - Organization identifier where the experiment will be created
- project
Id string - Project identifier where the experiment will be created
- template
Identity string - Identity of the experiment template to launch from
- description string
- Description of the chaos experiment
- hub
Org stringId - Organization identifier where the hub/template resides (leave empty for account-level hubs). This is used to locate the template, not where the experiment will be created.
- hub
Project stringId - Project identifier where the hub/template resides (leave empty for org-level or account-level hubs). This is used to locate the template, not where the experiment will be created.
- identity string
- Unique identifier for the experiment (auto-generated if not provided)
- import
Type string - Import type: REFERENCE (template reference) or LOCAL (full copy). Default: REFERENCE
- name string
- Name of the chaos experiment
- revision string
- Template revision to use (default: v1)
- string[]
- Tags to categorize the experiment. Note: Only user-configured tags are tracked in state. The API may add system-generated tags which are automatically filtered to prevent drift.
- hub_
identity str - Identity of the hub where the experiment template resides. Must include scope prefix for account and org levels: 'account.my-hub' for account-level hubs, 'org.my-hub' for org-level hubs, or just 'my-hub' for project-level hubs (no prefix)
- infra_
ref str - Infrastructure reference (ID or identity) to bind the experiment to
- org_
id str - Organization identifier where the experiment will be created
- project_
id str - Project identifier where the experiment will be created
- template_
identity str - Identity of the experiment template to launch from
- description str
- Description of the chaos experiment
- hub_
org_ strid - Organization identifier where the hub/template resides (leave empty for account-level hubs). This is used to locate the template, not where the experiment will be created.
- hub_
project_ strid - Project identifier where the hub/template resides (leave empty for org-level or account-level hubs). This is used to locate the template, not where the experiment will be created.
- identity str
- Unique identifier for the experiment (auto-generated if not provided)
- import_
type str - Import type: REFERENCE (template reference) or LOCAL (full copy). Default: REFERENCE
- name str
- Name of the chaos experiment
- revision str
- Template revision to use (default: v1)
- Sequence[str]
- Tags to categorize the experiment. Note: Only user-configured tags are tracked in state. The API may add system-generated tags which are automatically filtered to prevent drift.
- hub
Identity String - Identity of the hub where the experiment template resides. Must include scope prefix for account and org levels: 'account.my-hub' for account-level hubs, 'org.my-hub' for org-level hubs, or just 'my-hub' for project-level hubs (no prefix)
- infra
Ref String - Infrastructure reference (ID or identity) to bind the experiment to
- org
Id String - Organization identifier where the experiment will be created
- project
Id String - Project identifier where the experiment will be created
- template
Identity String - Identity of the experiment template to launch from
- description String
- Description of the chaos experiment
- hub
Org StringId - Organization identifier where the hub/template resides (leave empty for account-level hubs). This is used to locate the template, not where the experiment will be created.
- hub
Project StringId - Project identifier where the hub/template resides (leave empty for org-level or account-level hubs). This is used to locate the template, not where the experiment will be created.
- identity String
- Unique identifier for the experiment (auto-generated if not provided)
- import
Type String - Import type: REFERENCE (template reference) or LOCAL (full copy). Default: REFERENCE
- name String
- Name of the chaos experiment
- revision String
- Template revision to use (default: v1)
- List<String>
- Tags to categorize the experiment. Note: Only user-configured tags are tracked in state. The API may add system-generated tags which are automatically filtered to prevent drift.
Outputs
All input properties are implicitly available as output properties. Additionally, the Experiment resource produces the following output properties:
- Created
At int - Creation timestamp (Unix)
- Created
By string - Username of the creator
- Cron
Syntax string - Cron expression for scheduled execution
- Experiment
Id string - Full experiment ID
- Experiment
Type string - Type of the experiment
- Fault
Ids List<string> - List of fault IDs used in the experiment
- Id string
- The provider-assigned unique ID for this managed resource.
- Infra
Id string - Resolved infrastructure ID
- Infra
Type string - Infrastructure type (e.g., KubernetesV2)
- Is
Cron boolEnabled - Whether cron scheduling is enabled
- Is
Custom boolExperiment - Whether this is a custom experiment
- Is
Single boolRun Cron Enabled - Whether single-run cron is enabled
- Last
Executed intAt - Timestamp of last execution
- Manifest string
- Full experiment manifest YAML (populated for LOCAL imports)
- Target
Network stringMap Id - Target network map ID
- Template
Details List<ExperimentTemplate Detail> - Details about the experiment template used
- Total
Experiment intRuns - Total number of experiment runs
- Updated
At int - Last update timestamp (Unix)
- Updated
By string - Username of the last updater
- Created
At int - Creation timestamp (Unix)
- Created
By string - Username of the creator
- Cron
Syntax string - Cron expression for scheduled execution
- Experiment
Id string - Full experiment ID
- Experiment
Type string - Type of the experiment
- Fault
Ids []string - List of fault IDs used in the experiment
- Id string
- The provider-assigned unique ID for this managed resource.
- Infra
Id string - Resolved infrastructure ID
- Infra
Type string - Infrastructure type (e.g., KubernetesV2)
- Is
Cron boolEnabled - Whether cron scheduling is enabled
- Is
Custom boolExperiment - Whether this is a custom experiment
- Is
Single boolRun Cron Enabled - Whether single-run cron is enabled
- Last
Executed intAt - Timestamp of last execution
- Manifest string
- Full experiment manifest YAML (populated for LOCAL imports)
- Target
Network stringMap Id - Target network map ID
- Template
Details []ExperimentTemplate Detail - Details about the experiment template used
- Total
Experiment intRuns - Total number of experiment runs
- Updated
At int - Last update timestamp (Unix)
- Updated
By string - Username of the last updater
- created
At Integer - Creation timestamp (Unix)
- created
By String - Username of the creator
- cron
Syntax String - Cron expression for scheduled execution
- experiment
Id String - Full experiment ID
- experiment
Type String - Type of the experiment
- fault
Ids List<String> - List of fault IDs used in the experiment
- id String
- The provider-assigned unique ID for this managed resource.
- infra
Id String - Resolved infrastructure ID
- infra
Type String - Infrastructure type (e.g., KubernetesV2)
- is
Cron BooleanEnabled - Whether cron scheduling is enabled
- is
Custom BooleanExperiment - Whether this is a custom experiment
- is
Single BooleanRun Cron Enabled - Whether single-run cron is enabled
- last
Executed IntegerAt - Timestamp of last execution
- manifest String
- Full experiment manifest YAML (populated for LOCAL imports)
- target
Network StringMap Id - Target network map ID
- template
Details List<ExperimentTemplate Detail> - Details about the experiment template used
- total
Experiment IntegerRuns - Total number of experiment runs
- updated
At Integer - Last update timestamp (Unix)
- updated
By String - Username of the last updater
- created
At number - Creation timestamp (Unix)
- created
By string - Username of the creator
- cron
Syntax string - Cron expression for scheduled execution
- experiment
Id string - Full experiment ID
- experiment
Type string - Type of the experiment
- fault
Ids string[] - List of fault IDs used in the experiment
- id string
- The provider-assigned unique ID for this managed resource.
- infra
Id string - Resolved infrastructure ID
- infra
Type string - Infrastructure type (e.g., KubernetesV2)
- is
Cron booleanEnabled - Whether cron scheduling is enabled
- is
Custom booleanExperiment - Whether this is a custom experiment
- is
Single booleanRun Cron Enabled - Whether single-run cron is enabled
- last
Executed numberAt - Timestamp of last execution
- manifest string
- Full experiment manifest YAML (populated for LOCAL imports)
- target
Network stringMap Id - Target network map ID
- template
Details ExperimentTemplate Detail[] - Details about the experiment template used
- total
Experiment numberRuns - Total number of experiment runs
- updated
At number - Last update timestamp (Unix)
- updated
By string - Username of the last updater
- created_
at int - Creation timestamp (Unix)
- created_
by str - Username of the creator
- cron_
syntax str - Cron expression for scheduled execution
- experiment_
id str - Full experiment ID
- experiment_
type str - Type of the experiment
- fault_
ids Sequence[str] - List of fault IDs used in the experiment
- id str
- The provider-assigned unique ID for this managed resource.
- infra_
id str - Resolved infrastructure ID
- infra_
type str - Infrastructure type (e.g., KubernetesV2)
- is_
cron_ boolenabled - Whether cron scheduling is enabled
- is_
custom_ boolexperiment - Whether this is a custom experiment
- is_
single_ boolrun_ cron_ enabled - Whether single-run cron is enabled
- last_
executed_ intat - Timestamp of last execution
- manifest str
- Full experiment manifest YAML (populated for LOCAL imports)
- target_
network_ strmap_ id - Target network map ID
- template_
details Sequence[ExperimentTemplate Detail] - Details about the experiment template used
- total_
experiment_ intruns - Total number of experiment runs
- updated_
at int - Last update timestamp (Unix)
- updated_
by str - Username of the last updater
- created
At Number - Creation timestamp (Unix)
- created
By String - Username of the creator
- cron
Syntax String - Cron expression for scheduled execution
- experiment
Id String - Full experiment ID
- experiment
Type String - Type of the experiment
- fault
Ids List<String> - List of fault IDs used in the experiment
- id String
- The provider-assigned unique ID for this managed resource.
- infra
Id String - Resolved infrastructure ID
- infra
Type String - Infrastructure type (e.g., KubernetesV2)
- is
Cron BooleanEnabled - Whether cron scheduling is enabled
- is
Custom BooleanExperiment - Whether this is a custom experiment
- is
Single BooleanRun Cron Enabled - Whether single-run cron is enabled
- last
Executed NumberAt - Timestamp of last execution
- manifest String
- Full experiment manifest YAML (populated for LOCAL imports)
- target
Network StringMap Id - Target network map ID
- template
Details List<Property Map> - Details about the experiment template used
- total
Experiment NumberRuns - Total number of experiment runs
- updated
At Number - Last update timestamp (Unix)
- updated
By String - Username of the last updater
Look up Existing Experiment Resource
Get an existing Experiment resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: ExperimentState, opts?: CustomResourceOptions): Experiment@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
created_at: Optional[int] = None,
created_by: Optional[str] = None,
cron_syntax: Optional[str] = None,
description: Optional[str] = None,
experiment_id: Optional[str] = None,
experiment_type: Optional[str] = None,
fault_ids: Optional[Sequence[str]] = None,
hub_identity: Optional[str] = None,
hub_org_id: Optional[str] = None,
hub_project_id: Optional[str] = None,
identity: Optional[str] = None,
import_type: Optional[str] = None,
infra_id: Optional[str] = None,
infra_ref: Optional[str] = None,
infra_type: Optional[str] = None,
is_cron_enabled: Optional[bool] = None,
is_custom_experiment: Optional[bool] = None,
is_single_run_cron_enabled: Optional[bool] = None,
last_executed_at: Optional[int] = None,
manifest: Optional[str] = None,
name: Optional[str] = None,
org_id: Optional[str] = None,
project_id: Optional[str] = None,
revision: Optional[str] = None,
tags: Optional[Sequence[str]] = None,
target_network_map_id: Optional[str] = None,
template_details: Optional[Sequence[ExperimentTemplateDetailArgs]] = None,
template_identity: Optional[str] = None,
total_experiment_runs: Optional[int] = None,
updated_at: Optional[int] = None,
updated_by: Optional[str] = None) -> Experimentfunc GetExperiment(ctx *Context, name string, id IDInput, state *ExperimentState, opts ...ResourceOption) (*Experiment, error)public static Experiment Get(string name, Input<string> id, ExperimentState? state, CustomResourceOptions? opts = null)public static Experiment get(String name, Output<String> id, ExperimentState state, CustomResourceOptions options)resources: _: type: harness:chaos:Experiment get: id: ${id}- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- Created
At int - Creation timestamp (Unix)
- Created
By string - Username of the creator
- Cron
Syntax string - Cron expression for scheduled execution
- Description string
- Description of the chaos experiment
- Experiment
Id string - Full experiment ID
- Experiment
Type string - Type of the experiment
- Fault
Ids List<string> - List of fault IDs used in the experiment
- Hub
Identity string - Identity of the hub where the experiment template resides. Must include scope prefix for account and org levels: 'account.my-hub' for account-level hubs, 'org.my-hub' for org-level hubs, or just 'my-hub' for project-level hubs (no prefix)
- Hub
Org stringId - Organization identifier where the hub/template resides (leave empty for account-level hubs). This is used to locate the template, not where the experiment will be created.
- Hub
Project stringId - Project identifier where the hub/template resides (leave empty for org-level or account-level hubs). This is used to locate the template, not where the experiment will be created.
- Identity string
- Unique identifier for the experiment (auto-generated if not provided)
- Import
Type string - Import type: REFERENCE (template reference) or LOCAL (full copy). Default: REFERENCE
- Infra
Id string - Resolved infrastructure ID
- Infra
Ref string - Infrastructure reference (ID or identity) to bind the experiment to
- Infra
Type string - Infrastructure type (e.g., KubernetesV2)
- Is
Cron boolEnabled - Whether cron scheduling is enabled
- Is
Custom boolExperiment - Whether this is a custom experiment
- Is
Single boolRun Cron Enabled - Whether single-run cron is enabled
- Last
Executed intAt - Timestamp of last execution
- Manifest string
- Full experiment manifest YAML (populated for LOCAL imports)
- Name string
- Name of the chaos experiment
- Org
Id string - Organization identifier where the experiment will be created
- Project
Id string - Project identifier where the experiment will be created
- Revision string
- Template revision to use (default: v1)
- List<string>
- Tags to categorize the experiment. Note: Only user-configured tags are tracked in state. The API may add system-generated tags which are automatically filtered to prevent drift.
- Target
Network stringMap Id - Target network map ID
- Template
Details List<ExperimentTemplate Detail> - Details about the experiment template used
- Template
Identity string - Identity of the experiment template to launch from
- Total
Experiment intRuns - Total number of experiment runs
- Updated
At int - Last update timestamp (Unix)
- Updated
By string - Username of the last updater
- Created
At int - Creation timestamp (Unix)
- Created
By string - Username of the creator
- Cron
Syntax string - Cron expression for scheduled execution
- Description string
- Description of the chaos experiment
- Experiment
Id string - Full experiment ID
- Experiment
Type string - Type of the experiment
- Fault
Ids []string - List of fault IDs used in the experiment
- Hub
Identity string - Identity of the hub where the experiment template resides. Must include scope prefix for account and org levels: 'account.my-hub' for account-level hubs, 'org.my-hub' for org-level hubs, or just 'my-hub' for project-level hubs (no prefix)
- Hub
Org stringId - Organization identifier where the hub/template resides (leave empty for account-level hubs). This is used to locate the template, not where the experiment will be created.
- Hub
Project stringId - Project identifier where the hub/template resides (leave empty for org-level or account-level hubs). This is used to locate the template, not where the experiment will be created.
- Identity string
- Unique identifier for the experiment (auto-generated if not provided)
- Import
Type string - Import type: REFERENCE (template reference) or LOCAL (full copy). Default: REFERENCE
- Infra
Id string - Resolved infrastructure ID
- Infra
Ref string - Infrastructure reference (ID or identity) to bind the experiment to
- Infra
Type string - Infrastructure type (e.g., KubernetesV2)
- Is
Cron boolEnabled - Whether cron scheduling is enabled
- Is
Custom boolExperiment - Whether this is a custom experiment
- Is
Single boolRun Cron Enabled - Whether single-run cron is enabled
- Last
Executed intAt - Timestamp of last execution
- Manifest string
- Full experiment manifest YAML (populated for LOCAL imports)
- Name string
- Name of the chaos experiment
- Org
Id string - Organization identifier where the experiment will be created
- Project
Id string - Project identifier where the experiment will be created
- Revision string
- Template revision to use (default: v1)
- []string
- Tags to categorize the experiment. Note: Only user-configured tags are tracked in state. The API may add system-generated tags which are automatically filtered to prevent drift.
- Target
Network stringMap Id - Target network map ID
- Template
Details []ExperimentTemplate Detail Args - Details about the experiment template used
- Template
Identity string - Identity of the experiment template to launch from
- Total
Experiment intRuns - Total number of experiment runs
- Updated
At int - Last update timestamp (Unix)
- Updated
By string - Username of the last updater
- created
At Integer - Creation timestamp (Unix)
- created
By String - Username of the creator
- cron
Syntax String - Cron expression for scheduled execution
- description String
- Description of the chaos experiment
- experiment
Id String - Full experiment ID
- experiment
Type String - Type of the experiment
- fault
Ids List<String> - List of fault IDs used in the experiment
- hub
Identity String - Identity of the hub where the experiment template resides. Must include scope prefix for account and org levels: 'account.my-hub' for account-level hubs, 'org.my-hub' for org-level hubs, or just 'my-hub' for project-level hubs (no prefix)
- hub
Org StringId - Organization identifier where the hub/template resides (leave empty for account-level hubs). This is used to locate the template, not where the experiment will be created.
- hub
Project StringId - Project identifier where the hub/template resides (leave empty for org-level or account-level hubs). This is used to locate the template, not where the experiment will be created.
- identity String
- Unique identifier for the experiment (auto-generated if not provided)
- import
Type String - Import type: REFERENCE (template reference) or LOCAL (full copy). Default: REFERENCE
- infra
Id String - Resolved infrastructure ID
- infra
Ref String - Infrastructure reference (ID or identity) to bind the experiment to
- infra
Type String - Infrastructure type (e.g., KubernetesV2)
- is
Cron BooleanEnabled - Whether cron scheduling is enabled
- is
Custom BooleanExperiment - Whether this is a custom experiment
- is
Single BooleanRun Cron Enabled - Whether single-run cron is enabled
- last
Executed IntegerAt - Timestamp of last execution
- manifest String
- Full experiment manifest YAML (populated for LOCAL imports)
- name String
- Name of the chaos experiment
- org
Id String - Organization identifier where the experiment will be created
- project
Id String - Project identifier where the experiment will be created
- revision String
- Template revision to use (default: v1)
- List<String>
- Tags to categorize the experiment. Note: Only user-configured tags are tracked in state. The API may add system-generated tags which are automatically filtered to prevent drift.
- target
Network StringMap Id - Target network map ID
- template
Details List<ExperimentTemplate Detail> - Details about the experiment template used
- template
Identity String - Identity of the experiment template to launch from
- total
Experiment IntegerRuns - Total number of experiment runs
- updated
At Integer - Last update timestamp (Unix)
- updated
By String - Username of the last updater
- created
At number - Creation timestamp (Unix)
- created
By string - Username of the creator
- cron
Syntax string - Cron expression for scheduled execution
- description string
- Description of the chaos experiment
- experiment
Id string - Full experiment ID
- experiment
Type string - Type of the experiment
- fault
Ids string[] - List of fault IDs used in the experiment
- hub
Identity string - Identity of the hub where the experiment template resides. Must include scope prefix for account and org levels: 'account.my-hub' for account-level hubs, 'org.my-hub' for org-level hubs, or just 'my-hub' for project-level hubs (no prefix)
- hub
Org stringId - Organization identifier where the hub/template resides (leave empty for account-level hubs). This is used to locate the template, not where the experiment will be created.
- hub
Project stringId - Project identifier where the hub/template resides (leave empty for org-level or account-level hubs). This is used to locate the template, not where the experiment will be created.
- identity string
- Unique identifier for the experiment (auto-generated if not provided)
- import
Type string - Import type: REFERENCE (template reference) or LOCAL (full copy). Default: REFERENCE
- infra
Id string - Resolved infrastructure ID
- infra
Ref string - Infrastructure reference (ID or identity) to bind the experiment to
- infra
Type string - Infrastructure type (e.g., KubernetesV2)
- is
Cron booleanEnabled - Whether cron scheduling is enabled
- is
Custom booleanExperiment - Whether this is a custom experiment
- is
Single booleanRun Cron Enabled - Whether single-run cron is enabled
- last
Executed numberAt - Timestamp of last execution
- manifest string
- Full experiment manifest YAML (populated for LOCAL imports)
- name string
- Name of the chaos experiment
- org
Id string - Organization identifier where the experiment will be created
- project
Id string - Project identifier where the experiment will be created
- revision string
- Template revision to use (default: v1)
- string[]
- Tags to categorize the experiment. Note: Only user-configured tags are tracked in state. The API may add system-generated tags which are automatically filtered to prevent drift.
- target
Network stringMap Id - Target network map ID
- template
Details ExperimentTemplate Detail[] - Details about the experiment template used
- template
Identity string - Identity of the experiment template to launch from
- total
Experiment numberRuns - Total number of experiment runs
- updated
At number - Last update timestamp (Unix)
- updated
By string - Username of the last updater
- created_
at int - Creation timestamp (Unix)
- created_
by str - Username of the creator
- cron_
syntax str - Cron expression for scheduled execution
- description str
- Description of the chaos experiment
- experiment_
id str - Full experiment ID
- experiment_
type str - Type of the experiment
- fault_
ids Sequence[str] - List of fault IDs used in the experiment
- hub_
identity str - Identity of the hub where the experiment template resides. Must include scope prefix for account and org levels: 'account.my-hub' for account-level hubs, 'org.my-hub' for org-level hubs, or just 'my-hub' for project-level hubs (no prefix)
- hub_
org_ strid - Organization identifier where the hub/template resides (leave empty for account-level hubs). This is used to locate the template, not where the experiment will be created.
- hub_
project_ strid - Project identifier where the hub/template resides (leave empty for org-level or account-level hubs). This is used to locate the template, not where the experiment will be created.
- identity str
- Unique identifier for the experiment (auto-generated if not provided)
- import_
type str - Import type: REFERENCE (template reference) or LOCAL (full copy). Default: REFERENCE
- infra_
id str - Resolved infrastructure ID
- infra_
ref str - Infrastructure reference (ID or identity) to bind the experiment to
- infra_
type str - Infrastructure type (e.g., KubernetesV2)
- is_
cron_ boolenabled - Whether cron scheduling is enabled
- is_
custom_ boolexperiment - Whether this is a custom experiment
- is_
single_ boolrun_ cron_ enabled - Whether single-run cron is enabled
- last_
executed_ intat - Timestamp of last execution
- manifest str
- Full experiment manifest YAML (populated for LOCAL imports)
- name str
- Name of the chaos experiment
- org_
id str - Organization identifier where the experiment will be created
- project_
id str - Project identifier where the experiment will be created
- revision str
- Template revision to use (default: v1)
- Sequence[str]
- Tags to categorize the experiment. Note: Only user-configured tags are tracked in state. The API may add system-generated tags which are automatically filtered to prevent drift.
- target_
network_ strmap_ id - Target network map ID
- template_
details Sequence[ExperimentTemplate Detail Args] - Details about the experiment template used
- template_
identity str - Identity of the experiment template to launch from
- total_
experiment_ intruns - Total number of experiment runs
- updated_
at int - Last update timestamp (Unix)
- updated_
by str - Username of the last updater
- created
At Number - Creation timestamp (Unix)
- created
By String - Username of the creator
- cron
Syntax String - Cron expression for scheduled execution
- description String
- Description of the chaos experiment
- experiment
Id String - Full experiment ID
- experiment
Type String - Type of the experiment
- fault
Ids List<String> - List of fault IDs used in the experiment
- hub
Identity String - Identity of the hub where the experiment template resides. Must include scope prefix for account and org levels: 'account.my-hub' for account-level hubs, 'org.my-hub' for org-level hubs, or just 'my-hub' for project-level hubs (no prefix)
- hub
Org StringId - Organization identifier where the hub/template resides (leave empty for account-level hubs). This is used to locate the template, not where the experiment will be created.
- hub
Project StringId - Project identifier where the hub/template resides (leave empty for org-level or account-level hubs). This is used to locate the template, not where the experiment will be created.
- identity String
- Unique identifier for the experiment (auto-generated if not provided)
- import
Type String - Import type: REFERENCE (template reference) or LOCAL (full copy). Default: REFERENCE
- infra
Id String - Resolved infrastructure ID
- infra
Ref String - Infrastructure reference (ID or identity) to bind the experiment to
- infra
Type String - Infrastructure type (e.g., KubernetesV2)
- is
Cron BooleanEnabled - Whether cron scheduling is enabled
- is
Custom BooleanExperiment - Whether this is a custom experiment
- is
Single BooleanRun Cron Enabled - Whether single-run cron is enabled
- last
Executed NumberAt - Timestamp of last execution
- manifest String
- Full experiment manifest YAML (populated for LOCAL imports)
- name String
- Name of the chaos experiment
- org
Id String - Organization identifier where the experiment will be created
- project
Id String - Project identifier where the experiment will be created
- revision String
- Template revision to use (default: v1)
- List<String>
- Tags to categorize the experiment. Note: Only user-configured tags are tracked in state. The API may add system-generated tags which are automatically filtered to prevent drift.
- target
Network StringMap Id - Target network map ID
- template
Details List<Property Map> - Details about the experiment template used
- template
Identity String - Identity of the experiment template to launch from
- total
Experiment NumberRuns - Total number of experiment runs
- updated
At Number - Last update timestamp (Unix)
- updated
By String - Username of the last updater
Supporting Types
ExperimentTemplateDetail, ExperimentTemplateDetailArgs
- Hub
Reference string - Hub reference where template resides
- Identity string
- Template identity
- Reference string
- Full template reference
- Revision string
- Template revision used
- Hub
Reference string - Hub reference where template resides
- Identity string
- Template identity
- Reference string
- Full template reference
- Revision string
- Template revision used
- hub
Reference String - Hub reference where template resides
- identity String
- Template identity
- reference String
- Full template reference
- revision String
- Template revision used
- hub
Reference string - Hub reference where template resides
- identity string
- Template identity
- reference string
- Full template reference
- revision string
- Template revision used
- hub_
reference str - Hub reference where template resides
- identity str
- Template identity
- reference str
- Full template reference
- revision str
- Template revision used
- hub
Reference String - Hub reference where template resides
- identity String
- Template identity
- reference String
- Full template reference
- revision String
- Template revision used
Import
The pulumi import command can be used, for example:
!/bin/bash
Harness Chaos Experiment Import Examples
Import Format: org_id/project_id/experiment_identity
============================================================================
Example 1: Import Project-Level Experiment
$ pulumi import harness:chaos/experiment:Experiment basic my_org/my_project/my-chaos-experiment
After Import
- Run
terraform state show harness_chaos_experiment.exampleto see imported values - Run
pulumi previewto check for configuration drift - Update your .tf file to match the imported state
Required configuration after import:
- org_id, projectId
- hub_org_id, hub_project_id, hubIdentity
- templateIdentity
- name, infraRef
- importType (default: “REFERENCE”)
To learn more about importing existing cloud resources, see Importing resources.
Package Details
- Repository
- harness pulumi/pulumi-harness
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
harnessTerraform Provider.
published on Tuesday, Apr 21, 2026 by Pulumi
