Back to index
Summary
Seeds the environment with a new inventory to mimic an actual application or release-scoped deployment.projectNameStringrequiredThe name for the project that must be unique among all projects. environmentNameStringrequiredThe name of the environment. applicationNameStringrequiredApplications that owns the inventory item. statusStringrequiredInventory deployment status. Possible values: "success" , "warning" , "error" , "skipped" , "notRun" applicationProcessNameStringoptionalApplication process used to deploy to the environment. applicationTierNameStringoptionalThe name of the application tier. applicationVersionStringoptionalApplication version for the application that was deployed. artifactNameStringoptionalArtifact name for the inventory item. artifactProviderSourceStringoptionalSource of the provider that indirectly owns this artifact. artifactSourceStringoptionalSource of the artifact. artifactUrlStringoptionalUrl of the artifact. If using an IPv6 address, enclose the address in square brackets. Example: [<IPv6-ADDRESS>] .artifactVersionStringoptionalArtifact version for the inventory item. clusterNameStringoptionalCluster where the item is installed. clusterNamespaceStringoptionalCluster namespace where the item is installed. componentNameStringoptionalComponent that owns the inventory item. deploymentDetailsStringoptionalAdditional information about the deployment in JSON format. deploymentStrategyStringoptionalDeployment strategy used for the deployment of the microservice artifact being added to the environment inventory. (Used exclusively in the context of an advanced deployment strategy for a microservice application). Possible values: "canary" , "bluegreen" deploymentStrategyInProgressBooleanoptionalWhether deployment strategy is in progress. (Used exclusively in the context of an advanced deployment strategy for a microservice application). deploymentStrategyLabelStringoptionalLabel used by microservice plugins EC-Helm and EC-Kubectl to identify deployments depending on the deployment strategy in progress. For example, canary and stable will be used with canary strategy-based deployments while preview and active will be used with bluegreen strategy-based deployments. (Used exclusively in the context of an advanced deployment strategy for a microservice application). environmentProjectNameStringoptionalName for the project to which the environment or environment template belongs to. jobIdStringoptionalThe ID of the job. microserviceDeploymentDataStringoptionalThe deployment details related to a microservice deployment. microserviceDeploymentSummaryStringoptionalThe summary of microservice deployment. microserviceNameStringoptionalMicroservice that owns the inventory item. releaseNameStringoptionalName of the release. releaseProjectNameStringoptionalName of the release project. resourceNamesArray<Unknown>optionalAn array of resource names seededBooleanoptionalSeeded status. snapshotNameStringoptionalName of a snapshot. stageNameStringoptionalName of the stage. |
Usage
Groovy
import com.electriccloud.client.groovy.ElectricFlow import com.electriccloud.client.groovy.models.* ElectricFlow ef = new ElectricFlow() def result = ef.seedEnvironmentInventory( projectName: "test-projectName", environmentName: "test-environmentName", applicationName: "test-applicationName", status: "test-status" /* optional arguments */ )