Introduction
IBM Cloud® projects are a named collection of configurations that are used to manage and deploy related resources and Infrastructure as Code (IaC). Projects ensure that the IaC is always managed, secure, and compliant. Use the API to create, manage, and deploy by using projects.
SDKs for Node, Python, and Go are available to make it easier to programmatically access the API from your code. The client libraries that are provided by the SDKs implement best practices for using the API and reduce the amount of code that you need to write. The tab for each language includes code examples that demonstrate how to use the client libraries.
For more information about using projects, see Learn about IaC deployments with projects.
Installing the Node SDK
npm install @ibm-cloud/project-node-client
View on GitHub
Installing the Python SDK
pip install ibm-project-sdk
Then in your code, you can import the service
from ibm_project_sdk.project_v1 import *
View on GitHub
Installing the Go SDK
Go modules (recommended): Add the following import in your code, and then run go build
or go mod tidy
import (
"github.com/IBM/project-go-sdk/projectv1"
)
Go get
go get -u github.com/IBM/project-go-sdk/1
View on GitHub
Endpoint URLs
The projects API uses the following global endpoint URL for all regions. When you call the API, add the path for each method to form the complete API endpoint for your requests. In the request examples, replace the {base_url}
parameter with the endpoint URL.
https://projects.api.cloud.ibm.com
Example API request
curl --request POST --header "content-type: application/json" --header "accept: application/json" --header "authorization: Bearer <IAM_token>" --data "{\"query\":\"string\"}" --url "https://projects.api.cloud.ibm.com"
Replace <IAM token>
in this example with your token value for your particular API call.
Authentication
The IBM Cloud projects API uses IBM Cloud Identity and Access Management (IAM) to authenticate requests.
To work with the API, authenticate your application or service by including your IBM Cloud IAM access token in API requests. In the request examples, replace any {IAM_Token}
and {iam_token}
parameters with the access token that you obtained from IAM.
To call each method, you need to be assigned a role that includes the required IAM actions. Each method lists the associated action. For more information about IAM actions and how they map to roles, see Assigning access to account management services.
To retrieve your access token, replace <API_KEY>
with your IAM API key:
curl -X POST "https://iam.cloud.ibm.com/identity/token" --header 'Content-Type: application/x-www-form-urlencoded' --header 'Accept: application/json' --data-urlencode 'grant_type=urn:ibm:params:oauth:grant-type:apikey' --data-urlencode 'apikey=<API_KEY>'
To use the API, replace {IAM_Token}
with the access token that you obtained from IAM, replace {http_method}
with an HTTP method such as GET
, and replace {url}
with a request URL such as
https://projects.api.cloud.ibm.com/projects?resource_group=Default&location=us-south"
:
curl -H "Authorization: Bearer {IAM_Token}" -X {http_method} "{url}"
Auditing
You can monitor API activity within your account by using the IBM Cloud Activity Tracker service. Whenever an API method is called, an event is generated that you can then track and audit from within Activity Tracker. The specific event type is listed for each individual method.
For more information about tracking project activity, see Auditing events for projects.
Error handling
This API uses standard HTTP status codes to indicate whether a method completed successfully. A 400
type response indicates a failure, and a 500
type response indicates an internal system error.
HTTP Error Code | Description | Recovery |
---|---|---|
400 |
Bad Request | The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all required parameters in your request. |
401 |
Unauthorized | You are not authorized to make this request. Log in to IBM Cloud and try again. If this error persists, contact the account owner to check your permissions. |
403 |
Forbidden | The supplied authentication is not authorized to access this resource. |
404 |
Not Found | The requested resource could not be found. |
405 |
Method Not Allowed | The requested resource doesn't support the request method. |
408 |
Request Timeout | The connection to the server timed out. Wait a few minutes, then try again. |
409 |
Conflict | The entity is already in the requested state. |
410 |
Gone | The requested resource is no longer available. |
429 |
Too many requests | Rate limiting in use. The user has sent too many requests. |
500 |
Internal Server Error | The request could not be completed by the server. It could be due to an internal error, or in some cases invalid data in the request. |
Pagination
The IBM Cloud Projects API endpoints to list projects (GET /v1/projects
), list configs (GET /v1/projects/{project_id}/configs
), and list environments (GET /v1/projects/{project_id}/environments
) can return many results. To improve performance, results are returned one page at a time, with a limited number of results on each page. The default page size is typically 10 items, with a maximum size of 100.
To specify a different page size, use the limit
query parameter.
For a request that uses pagination, the response includes extra properties:
- The
first.href
property links to the first page of resources - The
next.href
property links to the next page of resources (included for all pages except for the last page)
Use query parameters to page through your available resources and retrieve a subset of records. To
retrieve the first page of results, make the request without specifying a token
query parameter.
If the results cannot fit on the first page, the response will include a next
property, whose
value can then be specified as the token
parameter when the next page request is made. Each page of
results is based on the resources that exist at the time of each paginated request. Therefore, the results
might include resources that did not exist when the first request was made. The last page of results does not include a next
property.
Rate limiting
Rate limits for API requests are enforced based on the number of requests from a user ID or client ID. If the number of requests from a particular user ID or client IP reaches the request limit within the specified time window, no further requests are accepted until the timer expires. After the timer expires, a new time window begins with the next accepted request.
The response to each HTTP request includes headers that you can use to determine whether you are close to the rate limit:
RateLimit-Reset
: the time the current timer expires (in UNIX epoch time)RateLimit-Remaining
: the number of requests that remain in the current time windowRateLimit-Limit
: the total number of requests that are allowed within the time windowRetry-After
: the time to wait before a follow-up request is attempted
An HTTP status code of 429 indicates that the rate limit was exceeded.
The number of allowed requests and the length of the time window is the same for all methods and endpoints.
Change log
Important changes, such as additions, updates, and breaking changes, are marked with a change notice in this reference.
For a complete list of changes and improvements to this API, see the Projects API change log. Changes that require a new version are highlighted in the change log.
The configurations
response
models for all methods no longer use a pipeline_state
. All status information of a configuration
is available in the augmented state
property in the canonical schema of a configuration
. This update is a breaking change. For more information, see the Projects API change log for 6 November 2023.
Methods
Create a project
Create a new project and asynchronously setup the tools to manage it. Add a deployable architecture by customizing the configuration. After the changes are validated and approved, deploy the resources that the project configures. For more information, see Creating a project.
Create a new project and asynchronously setup the tools to manage it. Add a deployable architecture by customizing the configuration. After the changes are validated and approved, deploy the resources that the project configures. For more information, see Creating a project.
Create a new project and asynchronously setup the tools to manage it. Add a deployable architecture by customizing the configuration. After the changes are validated and approved, deploy the resources that the project configures. For more information, see Creating a project.
Create a new project and asynchronously setup the tools to manage it. Add a deployable architecture by customizing the configuration. After the changes are validated and approved, deploy the resources that the project configures. For more information, see Creating a project.
POST /v1/projects
create_project(
self,
definition: 'ProjectPrototypeDefinition',
location: str,
resource_group: str,
*,
configs: Optional[List['ProjectConfigPrototype']] = None,
environments: Optional[List['EnvironmentPrototype']] = None,
**kwargs,
) -> DetailedResponse
createProject(params)
(project *ProjectV1) CreateProject(createProjectOptions *CreateProjectOptions) (result *Project, response *core.DetailedResponse, err error)
(project *ProjectV1) CreateProjectWithContext(ctx context.Context, createProjectOptions *CreateProjectOptions) (result *Project, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the CreateProjectOptions
struct and set the fields to provide parameter values for the CreateProject
method.
A valid project definition document that adheres to the Project Definition schema.
A project example request with configurations.
{
"definition": {
"name": "acme-microservice",
"description": "A microservice to deploy on top of ACME infrastructure.",
"authorizations": {
"method": "trusted_profile",
"trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12"
}
},
"configs": [
{
"definition": {
"name": "account-stage",
"description": "The stage account configuration.",
"locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global"
}
},
{
"definition": {
"name": "env-stage",
"description": "The stage environment configuration that includes services common to all the environment regions.",
"locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global",
"inputs": {
"account_id": "ref:/configs/account-stage/inputs/account_id",
"resource_group": "stage",
"access_tags": [
"env:stage"
],
"logdna_name": "The name of the LogDNA stage service instance.",
"sysdig_name": "The name of the SysDig stage service instance."
}
}
},
{
"definition": {
"name": "region-us-south-stage",
"description": "The stage us-south configuration.",
"locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global"
}
},
{
"definition": {
"name": "region-eu-de-stage",
"description": "The stage eu-de configuration.",
"locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global",
"inputs": {
"account_id": "ref:/configs/account-stage/inputs/account_id",
"resource_group": "ref:/configs/env-stage/outputs/resource_group_id",
"logdna_id": "ref:/configs/env-stage/outputs/logdna_id",
"sysdig_id": "ref:/configs/env-stage/outputs/sysdig_id",
"access_tags": [
"region:eu-de"
]
}
}
}
],
"location": "us-south",
"resource_group": "Default"
}
An empty project example request.
{
"definition": {
"name": "acme-microservice",
"description": "A microservice to deploy on top of ACME infrastructure.",
"authorizations": {
"method": "trusted_profile",
"trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12"
}
},
"location": "us-south",
"resource_group": "Default"
}
An example request for project configurations environments.
{
"definition": {
"name": "acme-microservice",
"description": "A microservice to deploy on top of ACME infrastructure."
},
"environments": [
{
"definition": {
"name": "development",
"description": "The 'development' environment.",
"authorizations": {
"method": "trusted_profile",
"trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12"
},
"inputs": {
"resource_group": "stage",
"region": "us-south"
}
}
},
{
"definition": {
"name": "production",
"description": "The production environment."
}
}
],
"location": "us-south",
"resource_group": "Default"
}
A project example request for configurations by using a Schematics workspace.
{
"definition": {
"name": "acme-microservice",
"description": "A microservice to deploy on top of ACME infrastructure.",
"authorizations": {
"method": "trusted_profile",
"trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12"
}
},
"configs": [
{
"definition": {
"name": "account-stage",
"description": "The stage account configuration."
},
"schematics": {
"workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139"
}
}
],
"location": "us-south",
"resource_group": "Default"
}
The definition of the project.
The IBM Cloud location where a resource is deployed.
Allowable values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]The resource group name where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
^(?!\s)(?!.*\s$)[^'"`<>{}\x00-\x1F]*$
The project configurations. These configurations are included in the response of creating a project only if a configuration array is specified in the request payload.
Possible values: 0 ≤ number of items ≤ 100
Default:
[]
The project environment. These environments are included in the response of creating a project only if an environment array is specified in the request payload.
Possible values: 0 ≤ number of items ≤ 20
Default:
[]
parameters
The definition of the project.
- definition
The name of the project. It's unique within the account across regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The policy that indicates whether the resources are undeployed or not when a project is deleted.
Default:
true
A brief explanation of the project's use in the configuration of a deployable architecture. You can create a project without providing a description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
A boolean flag to enable auto deploy.
Default:
false
A boolean flag to enable automatic drift detection. Use this field to run a daily check to compare your configurations to your deployed resources to detect any difference.
Default:
false
The IBM Cloud location where a resource is deployed.
Allowable values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]Examples:The resource group name where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
Examples:The project configurations. These configurations are included in the response of creating a project only if a configuration array is specified in the request payload.
Possible values: 0 ≤ number of items ≤ 100
Default:
[]
Examples:- configs
The description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Allowable values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Allowable values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A Schematics workspace to use for deploying this deployable architecture.
If you are importing data from an existing Schematics workspace that is not backed by cart, then you must provide a
locator_id
. If you are using a Schematics workspace that is backed by cart, alocator_id
is not required because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
code is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace.
For more information, see Creating workspaces and importing your Terraform template.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
- If only a
The project environment. These environments are included in the response of creating a project only if an environment array is specified in the request payload.
Possible values: 0 ≤ number of items ≤ 20
Default:
[]
- environments
The environment definition.
- definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Allowable values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Allowable values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
parameters
The definition of the project.
- definition
The name of the project. It's unique within the account across regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The policy that indicates whether the resources are undeployed or not when a project is deleted.
Default:
true
A brief explanation of the project's use in the configuration of a deployable architecture. You can create a project without providing a description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
A boolean flag to enable auto deploy.
Default:
false
A boolean flag to enable automatic drift detection. Use this field to run a daily check to compare your configurations to your deployed resources to detect any difference.
Default:
false
The IBM Cloud location where a resource is deployed.
Allowable values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]Examples:The resource group name where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
Examples:The project configurations. These configurations are included in the response of creating a project only if a configuration array is specified in the request payload.
Possible values: 0 ≤ number of items ≤ 100
Default:
[]
Examples:- configs
The description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Allowable values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Allowable values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A Schematics workspace to use for deploying this deployable architecture.
If you are importing data from an existing Schematics workspace that is not backed by cart, then you must provide a
locator_id
. If you are using a Schematics workspace that is backed by cart, alocator_id
is not required because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
code is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace.
For more information, see Creating workspaces and importing your Terraform template.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
- If only a
The project environment. These environments are included in the response of creating a project only if an environment array is specified in the request payload.
Possible values: 0 ≤ number of items ≤ 20
Default:
[]
- environments
The environment definition.
- definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Allowable values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Allowable values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The CreateProject options.
The definition of the project.
Examples:{ "name": "acme-microservice", "description": "A microservice to deploy on top of ACME infrastructure.", "authorizations": { "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" } }
- Definition
The name of the project. It's unique within the account across regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The policy that indicates whether the resources are undeployed or not when a project is deleted.
Default:
true
A brief explanation of the project's use in the configuration of a deployable architecture. You can create a project without providing a description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
A boolean flag to enable auto deploy.
Default:
false
A boolean flag to enable automatic drift detection. Use this field to run a daily check to compare your configurations to your deployed resources to detect any difference.
Default:
false
The IBM Cloud location where a resource is deployed.
Allowable values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]Examples:us-south
The resource group name where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
Examples:Default
The project configurations. These configurations are included in the response of creating a project only if a configuration array is specified in the request payload.
Possible values: 0 ≤ number of items ≤ 100
Default:
[]
Examples:[ { "definition": { "name": "account-stage", "description": "The stage account configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global" } }, { "definition": { "name": "env-stage", "description": "The stage environment configuration that includes services common to all the environment regions.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "ref:/configs/account-stage/inputs/account_id", "resource_group": "stage", "access_tags": [ "env:stage" ], "logdna_name": "The name of the LogDNA stage service instance.", "sysdig_name": "The name of the SysDig stage service instance." } } }, { "definition": { "name": "region-us-south-stage", "description": "The stage us-south configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global" } }, { "definition": { "name": "region-eu-de-stage", "description": "The stage eu-de configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "ref:/configs/account-stage/inputs/account_id", "resource_group": "ref:/configs/env-stage/outputs/resource_group_id", "logdna_id": "ref:/configs/env-stage/outputs/logdna_id", "sysdig_id": "ref:/configs/env-stage/outputs/sysdig_id", "access_tags": [ "region:eu-de" ] } } } ]
- Configs
The description of a project configuration.
- Definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- ComplianceProfile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Allowable values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- Authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Allowable values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A Schematics workspace to use for deploying this deployable architecture.
If you are importing data from an existing Schematics workspace that is not backed by cart, then you must provide a
locator_id
. If you are using a Schematics workspace that is backed by cart, alocator_id
is not required because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
code is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace.
For more information, see Creating workspaces and importing your Terraform template.
- Schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
- If only a
The project environment. These environments are included in the response of creating a project only if an environment array is specified in the request payload.
Possible values: 0 ≤ number of items ≤ 20
Default:
[]
- Environments
The environment definition.
- Definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- Authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Allowable values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- ComplianceProfile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Allowable values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
curl -X POST --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" --header "Content-Type: application/json" --data '{ "definition": { "name": "acme-microservice", "description": "A microservice to deploy on top of ACME infrastructure.", "authorizations": { "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" } }, "configs": [ { "definition": { "name": "account-stage", "description": "The stage account configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global" } }, { "definition": { "name": "env-stage", "description": "The stage environment configuration that includes services common to all the environment regions.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "ref:/configs/account-stage/inputs/account_id", "resource_group": "stage", "access_tags": [ "env:stage" ], "logdna_name": "The name of the LogDNA stage service instance.", "sysdig_name": "The name of the SysDig stage service instance." } } }, { "definition": { "name": "region-us-south-stage", "description": "The stage us-south configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global" } }, { "definition": { "name": "region-eu-de-stage", "description": "The stage eu-de configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "ref:/configs/account-stage/inputs/account_id", "resource_group": "ref:/configs/env-stage/outputs/resource_group_id", "logdna_id": "ref:/configs/env-stage/outputs/logdna_id", "sysdig_id": "ref:/configs/env-stage/outputs/sysdig_id", "access_tags": [ "region:eu-de" ] } } } ], "location": "us-south", "resource_group": "Default" }' "{base_url}/v1/projects"
projectPrototypeDefinitionModel := &projectv1.ProjectPrototypeDefinition{ Name: core.StringPtr("acme-microservice"), Description: core.StringPtr("A microservice to deploy on top of ACME infrastructure."), } projectConfigDefinitionPrototypeModel := &projectv1.ProjectConfigDefinitionPrototypeDAConfigDefinitionPropertiesPrototype{ LocatorID: core.StringPtr("1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global"), Description: core.StringPtr("The stage account configuration."), Name: core.StringPtr("account-stage"), } projectConfigPrototypeModel := &projectv1.ProjectConfigPrototype{ Definition: projectConfigDefinitionPrototypeModel, } createProjectOptions := projectService.NewCreateProjectOptions( projectPrototypeDefinitionModel, "us-south", "Default", ) createProjectOptions.SetConfigs([]projectv1.ProjectConfigPrototype{*projectConfigPrototypeModel}) project, response, err := projectService.CreateProject(createProjectOptions) if err != nil { panic(err) } b, _ := json.MarshalIndent(project, "", " ") fmt.Println(string(b))
// Request models needed by this operation. // ProjectPrototypeDefinition const projectPrototypeDefinitionModel = { name: 'acme-microservice', description: 'A microservice to deploy on top of ACME infrastructure.', }; // ProjectConfigDefinitionPrototypeDAConfigDefinitionPropertiesPrototype const projectConfigDefinitionPrototypeModel = { locator_id: '1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global', description: 'The stage account configuration.', name: 'account-stage', }; // ProjectConfigPrototype const projectConfigPrototypeModel = { definition: projectConfigDefinitionPrototypeModel, }; const params = { definition: projectPrototypeDefinitionModel, location: 'us-south', resourceGroup: 'Default', configs: [projectConfigPrototypeModel], }; let res; try { res = await projectService.createProject(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
project_prototype_definition_model = { 'name': 'acme-microservice', 'description': 'A microservice to deploy on top of ACME infrastructure.', } project_config_definition_prototype_model = { 'locator_id': '1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global', 'description': 'The stage account configuration.', 'name': 'account-stage', } project_config_prototype_model = { 'definition': project_config_definition_prototype_model, } response = project_service.create_project( definition=project_prototype_definition_model, location='us-south', resource_group='Default', configs=[project_config_prototype_model], ) project = response.get_result() print(json.dumps(project, indent=2))
Response
The standard schema of a project.
The project configurations. These configurations are only included in the response of creating a project if a configuration array is specified in the request payload.
Possible values: 0 ≤ number of items ≤ 100
The project environment. These environments are only included in the response if project environments were created on the project.
Possible values: 0 ≤ number of items ≤ 20
The definition of the project.
The resource group name where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
^(?!\s)(?!.*\s$)[^'"`<>{}\x00-\x1F]*$
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
(?!\s)(?!.*\s$)^(crn)[^'"`<>{}\s\x00-\x1F]*
Example:
crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The cumulative list of needs attention items for a project. If the view is successfully retrieved, an empty or nonempty array is returned.
Possible values: 0 ≤ number of items ≤ 50
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The IBM Cloud location where a resource is deployed.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
^(?!\s)(?!.*\s$)[^'"`<>{}\x00-\x1F]*$
The resource group ID where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
^[0-9a-zA-Z]+$
The project status value.
Possible values: [
ready
,deleting
,deleting_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(http(s)?:\/\/)[a-zA-Z0-9\$\-_\.+!\*'\(\),=&?\/]+$
The CRN of the Event Notifications instance if one is connected to this project.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
^$|^crn:v[0-9](:([A-Za-z0-9\-._~!$&'()*+,;=@/]|%[0-9A-Z]{2})*){8}$
A value of
true
indicates that the fetch of the needs attention items failed. This property only exists if there was an error when you retrieved the cumulative needs attention view.
The standard schema of a project.
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The cumulative list of needs attention items for a project. If the view is successfully retrieved, an empty or nonempty array is returned.
Possible values: 0 ≤ number of items ≤ 50
- cumulative_needs_attention_view
The event name.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
A unique ID for this individual event.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique ID for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version number of the configuration.
A value of
true
indicates that the fetch of the needs attention items failed. This property only exists if there was an error when you retrieved the cumulative needs attention view.The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The IBM Cloud location where a resource is deployed.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The resource group ID where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^[0-9a-zA-Z]+$/
The project status value.
Possible values: [
ready
,deleting
,deleting_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The resource group name where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The CRN of the Event Notifications instance if one is connected to this project.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^$|^crn:v[0-9](:([A-Za-z0-9\\-._~!$&'()*+,;=@\/]|%[0-9A-Z]{2})*){8}$/
The project configurations. These configurations are only included in the response of creating a project if a configuration array is specified in the request payload.
Possible values: 0 ≤ number of items ≤ 100
- configs
A summary of a project configuration version.
- approved_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A summary of a project configuration version.
- deployed_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The description of a project configuration.
- definition
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]
The project environment. These environments are only included in the response if project environments were created on the project.
Possible values: 0 ≤ number of items ≤ 20
- environments
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment definition that is used in the project collection.
- definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The definition of the project.
- definition
The name of the project. It's unique within the account across regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The policy that indicates whether the resources are destroyed or not when a project is deleted.
A brief explanation of the project's use in the configuration of a deployable architecture. You can create a project without providing a description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A boolean flag to enable auto deploy.
A boolean flag to enable automatic drift detection. Use this field to run a daily check to compare your configurations to your deployed resources to detect any difference.
The standard schema of a project.
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The cumulative list of needs attention items for a project. If the view is successfully retrieved, an empty or nonempty array is returned.
Possible values: 0 ≤ number of items ≤ 50
- cumulative_needs_attention_view
The event name.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
A unique ID for this individual event.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique ID for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version number of the configuration.
A value of
true
indicates that the fetch of the needs attention items failed. This property only exists if there was an error when you retrieved the cumulative needs attention view.The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The IBM Cloud location where a resource is deployed.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The resource group ID where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^[0-9a-zA-Z]+$/
The project status value.
Possible values: [
ready
,deleting
,deleting_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The resource group name where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The CRN of the Event Notifications instance if one is connected to this project.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^$|^crn:v[0-9](:([A-Za-z0-9\\-._~!$&'()*+,;=@\/]|%[0-9A-Z]{2})*){8}$/
The project configurations. These configurations are only included in the response of creating a project if a configuration array is specified in the request payload.
Possible values: 0 ≤ number of items ≤ 100
- configs
A summary of a project configuration version.
- approved_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A summary of a project configuration version.
- deployed_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The description of a project configuration.
- definition
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]
The project environment. These environments are only included in the response if project environments were created on the project.
Possible values: 0 ≤ number of items ≤ 20
- environments
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment definition that is used in the project collection.
- definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The definition of the project.
- definition
The name of the project. It's unique within the account across regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The policy that indicates whether the resources are destroyed or not when a project is deleted.
A brief explanation of the project's use in the configuration of a deployable architecture. You can create a project without providing a description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A boolean flag to enable auto deploy.
A boolean flag to enable automatic drift detection. Use this field to run a daily check to compare your configurations to your deployed resources to detect any difference.
The standard schema of a project.
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The cumulative list of needs attention items for a project. If the view is successfully retrieved, an empty or nonempty array is returned.
Possible values: 0 ≤ number of items ≤ 50
- CumulativeNeedsAttentionView
The event name.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
A unique ID for this individual event.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique ID for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version number of the configuration.
A value of
true
indicates that the fetch of the needs attention items failed. This property only exists if there was an error when you retrieved the cumulative needs attention view.The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The IBM Cloud location where a resource is deployed.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The resource group ID where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^[0-9a-zA-Z]+$/
The project status value.
Possible values: [
ready
,deleting
,deleting_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The resource group name where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The CRN of the Event Notifications instance if one is connected to this project.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^$|^crn:v[0-9](:([A-Za-z0-9\\-._~!$&'()*+,;=@\/]|%[0-9A-Z]{2})*){8}$/
The project configurations. These configurations are only included in the response of creating a project if a configuration array is specified in the request payload.
Possible values: 0 ≤ number of items ≤ 100
- Configs
A summary of a project configuration version.
- ApprovedVersion
A summary of the definition in a project configuration version.
- Definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A summary of a project configuration version.
- DeployedVersion
A summary of the definition in a project configuration version.
- Definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The description of a project configuration.
- Definition
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The project that is referenced by this resource.
- Project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- Definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]
The project environment. These environments are only included in the response if project environments were created on the project.
Possible values: 0 ≤ number of items ≤ 20
- Environments
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The project that is referenced by this resource.
- Project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- Definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment definition that is used in the project collection.
- Definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The definition of the project.
- Definition
The name of the project. It's unique within the account across regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The policy that indicates whether the resources are destroyed or not when a project is deleted.
A brief explanation of the project's use in the configuration of a deployable architecture. You can create a project without providing a description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A boolean flag to enable auto deploy.
A boolean flag to enable automatic drift detection. Use this field to run a daily check to compare your configurations to your deployed resources to detect any difference.
Status Code
OK
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The sample response to a request to retrieve an empty project.
{ "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.service.url/v1/projects/cfbf901-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "acme-microservice", "description": "A microservice to deploy on top of ACME infrastructure.", "auto_deploy": false, "destroy_on_delete": true, "monitoring_enabled": false }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "cumulative_needs_attention_view": [], "configs": [], "environments": [], "location": "us-south", "resource_group": "Default", "resource_group_id": "f37d2637ea814cfd9a1742683a713d24", "state": "ready" }
The sample response to a request to retrieve an empty project.
{ "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.service.url/v1/projects/cfbf901-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "acme-microservice", "description": "A microservice to deploy on top of ACME infrastructure.", "auto_deploy": false, "destroy_on_delete": true, "monitoring_enabled": false }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "cumulative_needs_attention_view": [], "configs": [], "environments": [], "location": "us-south", "resource_group": "Default", "resource_group_id": "f37d2637ea814cfd9a1742683a713d24", "state": "ready" }
The sample response to a request to retrieve a project with configurations.
{ "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.service.url/v1/projects/cfbf901-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "acme-microservice", "description": "A microservice to deploy on top of ACME infrastructure.", "auto_deploy": false, "destroy_on_delete": true, "monitoring_enabled": false }, "cumulative_needs_attention_view": [], "configs": [ { "id": "673d79e4-52bf-4184-b8e9-d3ca3c110f96", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "common-variables", "description": "The common-variables configuration." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/673d79e4-52bf-4184-b8e9-d3ca3c110f96", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "modified_at": "2023-02-22T19:51:23.253Z", "update_available": false, "version": 1 }, { "id": "4a1d4ba2-54ba-43a7-975a-d82b5a7612d1", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "account-stage", "description": "The stage account configuration. The stage account hosts test environments prestage, performance, stage." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/4a1d4ba2-54ba-43a7-975a-d82b5a7612d1", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 }, { "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "env-stage", "description": "The stage environment configuration. It includes services that are common to all the environment regions." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/293c3c36-a094-4115-a12b-de0a9ca39be5", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 }, { "id": "596e8656-9d4b-41a5-8340-b0cbe8bd374a", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "region-us-south-stage", "description": "The stage `us-south` configuration. You must have a blueprint that configures the Virtual Private Cloud and Red Hat OpenShift stage us-south." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/596e8656-9d4b-41a5-8340-b0cbe8bd374a", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 }, { "id": "9c7afed6-17fb-4c56-a13d-440a78f936bd", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "region-eu-de-stage", "description": "The stage `eu-de` configuration. You must have a blueprint that configures the Virtual Private Cloud and Red Hat OpenShift stage `eu-de`." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/9c7afed6-17fb-4c56-a13d-440a78f936bd", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 } ], "environments": [], "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "location": "us-south", "resource_group": "Default", "resource_group_id": "f37d2637ea814cfd9a1742683a713d24", "state": "ready" }
The sample response to a request to retrieve a project with configurations.
{ "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.service.url/v1/projects/cfbf901-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "acme-microservice", "description": "A microservice to deploy on top of ACME infrastructure.", "auto_deploy": false, "destroy_on_delete": true, "monitoring_enabled": false }, "cumulative_needs_attention_view": [], "configs": [ { "id": "673d79e4-52bf-4184-b8e9-d3ca3c110f96", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "common-variables", "description": "The common-variables configuration." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/673d79e4-52bf-4184-b8e9-d3ca3c110f96", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "modified_at": "2023-02-22T19:51:23.253Z", "update_available": false, "version": 1 }, { "id": "4a1d4ba2-54ba-43a7-975a-d82b5a7612d1", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "account-stage", "description": "The stage account configuration. The stage account hosts test environments prestage, performance, stage." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/4a1d4ba2-54ba-43a7-975a-d82b5a7612d1", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 }, { "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "env-stage", "description": "The stage environment configuration. It includes services that are common to all the environment regions." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/293c3c36-a094-4115-a12b-de0a9ca39be5", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 }, { "id": "596e8656-9d4b-41a5-8340-b0cbe8bd374a", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "region-us-south-stage", "description": "The stage `us-south` configuration. You must have a blueprint that configures the Virtual Private Cloud and Red Hat OpenShift stage us-south." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/596e8656-9d4b-41a5-8340-b0cbe8bd374a", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 }, { "id": "9c7afed6-17fb-4c56-a13d-440a78f936bd", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "region-eu-de-stage", "description": "The stage `eu-de` configuration. You must have a blueprint that configures the Virtual Private Cloud and Red Hat OpenShift stage `eu-de`." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/9c7afed6-17fb-4c56-a13d-440a78f936bd", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 } ], "environments": [], "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "location": "us-south", "resource_group": "Default", "resource_group_id": "f37d2637ea814cfd9a1742683a713d24", "state": "ready" }
The sample response to a request to retrieve a project with environments.
{ "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.service.url/v1/projects/cfbf901-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "acme-microservice", "description": "A microservice to deploy on top of ACME infrastructure.", "auto_deploy": false, "destroy_on_delete": true, "monitoring_enabled": false }, "cumulative_needs_attention_view": [], "configs": [], "environments": [ { "id": "b0c44146-1ef6-40c2-82ba-74d51149770a", "definition": { "name": "development", "description": "The development environment." }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "acme-microservice" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "created_at": "2023-02-10T10:05:35.787Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/environments/b0c44146-1ef6-40c2-82ba-74d51149770a" }, { "id": "9c7afed6-17fb-4c56-a13d-440a78f936bd", "definition": { "name": "production", "description": "The production environment." }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "acme-microservice" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "created_at": "2023-02-10T10:05:35.787Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/environments/9c7afed6-17fb-4c56-a13d-440a78f936bd" } ], "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "location": "us-south", "resource_group": "Default", "resource_group_id": "f37d2637ea814cfd9a1742683a713d24", "state": "ready" }
The sample response to a request to retrieve a project with environments.
{ "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.service.url/v1/projects/cfbf901-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "acme-microservice", "description": "A microservice to deploy on top of ACME infrastructure.", "auto_deploy": false, "destroy_on_delete": true, "monitoring_enabled": false }, "cumulative_needs_attention_view": [], "configs": [], "environments": [ { "id": "b0c44146-1ef6-40c2-82ba-74d51149770a", "definition": { "name": "development", "description": "The development environment." }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "acme-microservice" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "created_at": "2023-02-10T10:05:35.787Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/environments/b0c44146-1ef6-40c2-82ba-74d51149770a" }, { "id": "9c7afed6-17fb-4c56-a13d-440a78f936bd", "definition": { "name": "production", "description": "The production environment." }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "acme-microservice" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "created_at": "2023-02-10T10:05:35.787Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/environments/9c7afed6-17fb-4c56-a13d-440a78f936bd" } ], "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "location": "us-south", "resource_group": "Default", "resource_group_id": "f37d2637ea814cfd9a1742683a713d24", "state": "ready" }
List projects
List existing projects. Projects are sorted by ID.
List existing projects. Projects are sorted by ID.
List existing projects. Projects are sorted by ID.
List existing projects. Projects are sorted by ID.
GET /v1/projects
list_projects(
self,
*,
token: Optional[str] = None,
limit: Optional[int] = None,
**kwargs,
) -> DetailedResponse
listProjects(params)
(project *ProjectV1) ListProjects(listProjectsOptions *ListProjectsOptions) (result *ProjectCollection, response *core.DetailedResponse, err error)
(project *ProjectV1) ListProjectsWithContext(ctx context.Context, listProjectsOptions *ListProjectsOptions) (result *ProjectCollection, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the ListProjectsOptions
struct and set the fields to provide parameter values for the ListProjects
method.
Query Parameters
The server uses this parameter to determine the first entry that is returned on the next page. If this parameter is not specified, the logical first page is returned.
Possible values: 0 ≤ length ≤ 1536, Value must match regular expression
^$|^(?!\s)(?!.*\s$)[^\x00-\x1F]*$
Default:
The maximum number of resources to return. The number of resources that are returned is the same, except for the last page.
Possible values: 1 ≤ value ≤ 100
Default:
10
parameters
The server uses this parameter to determine the first entry that is returned on the next page. If this parameter is not specified, the logical first page is returned.
Possible values: 0 ≤ length ≤ 1536, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
The maximum number of resources to return. The number of resources that are returned is the same, except for the last page.
Possible values: 1 ≤ value ≤ 100
Default:
10
parameters
The server uses this parameter to determine the first entry that is returned on the next page. If this parameter is not specified, the logical first page is returned.
Possible values: 0 ≤ length ≤ 1536, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
The maximum number of resources to return. The number of resources that are returned is the same, except for the last page.
Possible values: 1 ≤ value ≤ 100
Default:
10
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The ListProjects options.
The server uses this parameter to determine the first entry that is returned on the next page. If this parameter is not specified, the logical first page is returned.
Possible values: 0 ≤ length ≤ 1536, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
The maximum number of resources to return. The number of resources that are returned is the same, except for the last page.
Possible values: 1 ≤ value ≤ 100
Default:
10
Examples:10
curl -X GET --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" "{base_url}/v1/projects"
listProjectsOptions := &projectv1.ListProjectsOptions{ Limit: core.Int64Ptr(int64(10)), } pager, err := projectService.NewProjectsPager(listProjectsOptions) if err != nil { panic(err) } var allResults []projectv1.ProjectSummary for pager.HasNext() { nextPage, err := pager.GetNext() if err != nil { panic(err) } allResults = append(allResults, nextPage...) } b, _ := json.MarshalIndent(allResults, "", " ") fmt.Println(string(b))
const params = { limit: 10, }; const allResults = []; try { const pager = new ProjectV1.ProjectsPager(projectService, params); while (pager.hasNext()) { const nextPage = await pager.getNext(); expect(nextPage).not.toBeNull(); allResults.push(...nextPage); } console.log(JSON.stringify(allResults, null, 2)); } catch (err) { console.warn(err); }
all_results = [] pager = ProjectsPager( client=project_service, limit=10, ) while pager.has_next(): next_page = pager.get_next() assert next_page is not None all_results.extend(next_page) print(json.dumps(all_results, indent=2))
Response
Projects list
A pagination limit.
Possible values: 1 ≤ value ≤ 100
A pagination link.
A pagination link.
An array of projects.
Possible values: 0 ≤ number of items ≤ 500
Projects list.
A pagination limit.
Possible values: 1 ≤ value ≤ 100
A pagination link.
- first
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A pagination link.
- next
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
An array of projects.
Possible values: 0 ≤ number of items ≤ 500
- projects
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The cumulative list of needs attention items for a project. If the view is successfully retrieved, an empty or nonempty array is returned.
Possible values: 0 ≤ number of items ≤ 50
- cumulative_needs_attention_view
The event name.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
A unique ID for this individual event.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique ID for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version number of the configuration.
A value of
true
indicates that the fetch of the needs attention items failed. This property only exists if there was an error when you retrieved the cumulative needs attention view.The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The IBM Cloud location where a resource is deployed.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The resource group ID where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^[0-9a-zA-Z]+$/
The project status value.
Possible values: [
ready
,deleting
,deleting_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project.
- definition
The name of the project. It's unique within the account across regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The policy that indicates whether the resources are destroyed or not when a project is deleted.
A brief explanation of the project's use in the configuration of a deployable architecture. You can create a project without providing a description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Projects list.
A pagination limit.
Possible values: 1 ≤ value ≤ 100
A pagination link.
- first
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A pagination link.
- next
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
An array of projects.
Possible values: 0 ≤ number of items ≤ 500
- projects
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The cumulative list of needs attention items for a project. If the view is successfully retrieved, an empty or nonempty array is returned.
Possible values: 0 ≤ number of items ≤ 50
- cumulative_needs_attention_view
The event name.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
A unique ID for this individual event.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique ID for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version number of the configuration.
A value of
true
indicates that the fetch of the needs attention items failed. This property only exists if there was an error when you retrieved the cumulative needs attention view.The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The IBM Cloud location where a resource is deployed.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The resource group ID where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^[0-9a-zA-Z]+$/
The project status value.
Possible values: [
ready
,deleting
,deleting_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project.
- definition
The name of the project. It's unique within the account across regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The policy that indicates whether the resources are destroyed or not when a project is deleted.
A brief explanation of the project's use in the configuration of a deployable architecture. You can create a project without providing a description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Projects list.
A pagination limit.
Possible values: 1 ≤ value ≤ 100
A pagination link.
- First
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A pagination link.
- Next
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
An array of projects.
Possible values: 0 ≤ number of items ≤ 500
- Projects
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The cumulative list of needs attention items for a project. If the view is successfully retrieved, an empty or nonempty array is returned.
Possible values: 0 ≤ number of items ≤ 50
- CumulativeNeedsAttentionView
The event name.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
A unique ID for this individual event.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique ID for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version number of the configuration.
A value of
true
indicates that the fetch of the needs attention items failed. This property only exists if there was an error when you retrieved the cumulative needs attention view.The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The IBM Cloud location where a resource is deployed.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The resource group ID where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^[0-9a-zA-Z]+$/
The project status value.
Possible values: [
ready
,deleting
,deleting_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project.
- Definition
The name of the project. It's unique within the account across regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The policy that indicates whether the resources are destroyed or not when a project is deleted.
A brief explanation of the project's use in the configuration of a deployable architecture. You can create a project without providing a description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Status Code
The request was successful.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
An example request to list projects.
{ "limit": 10, "first": { "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "next": { "href": "https://projects.api.cloud.ibm.com/v1/projects/12349050-1234-ac97-0000-ba5a12fe9087" }, "projects": [ { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.service.url/v1/projects/cfbf901-ab8e-ac97-b01b-ab5af830be8a", "definition": { "description": "A project example.", "name": "iaas-infra-prestage-env", "auto_deploy": false, "destroy_on_delete": false, "monitoring_enabled": false }, "location": "us-south", "state": "ready", "resource_group": "Default", "resource_group_id": "f37d2637ea814cfd9a1742683a713d24", "cumulative_needs_attention_view": [ { "event": "project.instance.update" }, { "event_id": "489f0090-6d7c-4af5-8f20-9106543e4974" }, { "config_id": "069ab83e-5016-4bf2-bd50-cc95cf678293" }, { "config_version": 1 } ] }, { "id": "1123ed42-4356-efa1-1101-235900fe9087", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.service.url/v1/projects/cfbf901-ab8e-ac97-b01b-ab5af830be8a", "definition": { "description": "A project example.", "name": "iaas-infra-stage-env", "auto_deploy": false, "destroy_on_delete": false, "monitoring_enabled": false }, "crn": "crn:v1:staging:public:project:eu-de:a/06580d923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "location": "eu-gb", "state": "ready", "resource_group": "Default", "resource_group_id": "f37d2637ea814cfd9a1742683a713d24", "cumulative_needs_attention_view": [] } ] }
An example request to list projects.
{ "limit": 10, "first": { "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "next": { "href": "https://projects.api.cloud.ibm.com/v1/projects/12349050-1234-ac97-0000-ba5a12fe9087" }, "projects": [ { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.service.url/v1/projects/cfbf901-ab8e-ac97-b01b-ab5af830be8a", "definition": { "description": "A project example.", "name": "iaas-infra-prestage-env", "auto_deploy": false, "destroy_on_delete": false, "monitoring_enabled": false }, "location": "us-south", "state": "ready", "resource_group": "Default", "resource_group_id": "f37d2637ea814cfd9a1742683a713d24", "cumulative_needs_attention_view": [ { "event": "project.instance.update" }, { "event_id": "489f0090-6d7c-4af5-8f20-9106543e4974" }, { "config_id": "069ab83e-5016-4bf2-bd50-cc95cf678293" }, { "config_version": 1 } ] }, { "id": "1123ed42-4356-efa1-1101-235900fe9087", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.service.url/v1/projects/cfbf901-ab8e-ac97-b01b-ab5af830be8a", "definition": { "description": "A project example.", "name": "iaas-infra-stage-env", "auto_deploy": false, "destroy_on_delete": false, "monitoring_enabled": false }, "crn": "crn:v1:staging:public:project:eu-de:a/06580d923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "location": "eu-gb", "state": "ready", "resource_group": "Default", "resource_group_id": "f37d2637ea814cfd9a1742683a713d24", "cumulative_needs_attention_view": [] } ] }
Get a project
Get information about a project.
Get information about a project.
Get information about a project.
Get information about a project.
GET /v1/projects/{id}
get_project(
self,
id: str,
**kwargs,
) -> DetailedResponse
getProject(params)
(project *ProjectV1) GetProject(getProjectOptions *GetProjectOptions) (result *Project, response *core.DetailedResponse, err error)
(project *ProjectV1) GetProjectWithContext(ctx context.Context, getProjectOptions *GetProjectOptions) (result *Project, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the GetProjectOptions
struct and set the fields to provide parameter values for the GetProject
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The GetProject options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
curl -X GET --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" "{base_url}/v1/projects/{id}"
getProjectOptions := projectService.NewGetProjectOptions( projectIdLink, ) project, response, err := projectService.GetProject(getProjectOptions) if err != nil { panic(err) } b, _ := json.MarshalIndent(project, "", " ") fmt.Println(string(b))
const params = { id: projectIdLink, }; let res; try { res = await projectService.getProject(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
response = project_service.get_project( id=project_id_link, ) project = response.get_result() print(json.dumps(project, indent=2))
Response
The standard schema of a project.
The project configurations. These configurations are only included in the response of creating a project if a configuration array is specified in the request payload.
Possible values: 0 ≤ number of items ≤ 100
The project environment. These environments are only included in the response if project environments were created on the project.
Possible values: 0 ≤ number of items ≤ 20
The definition of the project.
The resource group name where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
^(?!\s)(?!.*\s$)[^'"`<>{}\x00-\x1F]*$
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
(?!\s)(?!.*\s$)^(crn)[^'"`<>{}\s\x00-\x1F]*
Example:
crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The cumulative list of needs attention items for a project. If the view is successfully retrieved, an empty or nonempty array is returned.
Possible values: 0 ≤ number of items ≤ 50
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The IBM Cloud location where a resource is deployed.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
^(?!\s)(?!.*\s$)[^'"`<>{}\x00-\x1F]*$
The resource group ID where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
^[0-9a-zA-Z]+$
The project status value.
Possible values: [
ready
,deleting
,deleting_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(http(s)?:\/\/)[a-zA-Z0-9\$\-_\.+!\*'\(\),=&?\/]+$
The CRN of the Event Notifications instance if one is connected to this project.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
^$|^crn:v[0-9](:([A-Za-z0-9\-._~!$&'()*+,;=@/]|%[0-9A-Z]{2})*){8}$
A value of
true
indicates that the fetch of the needs attention items failed. This property only exists if there was an error when you retrieved the cumulative needs attention view.
The standard schema of a project.
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The cumulative list of needs attention items for a project. If the view is successfully retrieved, an empty or nonempty array is returned.
Possible values: 0 ≤ number of items ≤ 50
- cumulative_needs_attention_view
The event name.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
A unique ID for this individual event.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique ID for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version number of the configuration.
A value of
true
indicates that the fetch of the needs attention items failed. This property only exists if there was an error when you retrieved the cumulative needs attention view.The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The IBM Cloud location where a resource is deployed.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The resource group ID where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^[0-9a-zA-Z]+$/
The project status value.
Possible values: [
ready
,deleting
,deleting_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The resource group name where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The CRN of the Event Notifications instance if one is connected to this project.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^$|^crn:v[0-9](:([A-Za-z0-9\\-._~!$&'()*+,;=@\/]|%[0-9A-Z]{2})*){8}$/
The project configurations. These configurations are only included in the response of creating a project if a configuration array is specified in the request payload.
Possible values: 0 ≤ number of items ≤ 100
- configs
A summary of a project configuration version.
- approved_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A summary of a project configuration version.
- deployed_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The description of a project configuration.
- definition
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]
The project environment. These environments are only included in the response if project environments were created on the project.
Possible values: 0 ≤ number of items ≤ 20
- environments
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment definition that is used in the project collection.
- definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The definition of the project.
- definition
The name of the project. It's unique within the account across regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The policy that indicates whether the resources are destroyed or not when a project is deleted.
A brief explanation of the project's use in the configuration of a deployable architecture. You can create a project without providing a description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A boolean flag to enable auto deploy.
A boolean flag to enable automatic drift detection. Use this field to run a daily check to compare your configurations to your deployed resources to detect any difference.
The standard schema of a project.
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The cumulative list of needs attention items for a project. If the view is successfully retrieved, an empty or nonempty array is returned.
Possible values: 0 ≤ number of items ≤ 50
- cumulative_needs_attention_view
The event name.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
A unique ID for this individual event.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique ID for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version number of the configuration.
A value of
true
indicates that the fetch of the needs attention items failed. This property only exists if there was an error when you retrieved the cumulative needs attention view.The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The IBM Cloud location where a resource is deployed.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The resource group ID where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^[0-9a-zA-Z]+$/
The project status value.
Possible values: [
ready
,deleting
,deleting_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The resource group name where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The CRN of the Event Notifications instance if one is connected to this project.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^$|^crn:v[0-9](:([A-Za-z0-9\\-._~!$&'()*+,;=@\/]|%[0-9A-Z]{2})*){8}$/
The project configurations. These configurations are only included in the response of creating a project if a configuration array is specified in the request payload.
Possible values: 0 ≤ number of items ≤ 100
- configs
A summary of a project configuration version.
- approved_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A summary of a project configuration version.
- deployed_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The description of a project configuration.
- definition
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]
The project environment. These environments are only included in the response if project environments were created on the project.
Possible values: 0 ≤ number of items ≤ 20
- environments
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment definition that is used in the project collection.
- definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The definition of the project.
- definition
The name of the project. It's unique within the account across regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The policy that indicates whether the resources are destroyed or not when a project is deleted.
A brief explanation of the project's use in the configuration of a deployable architecture. You can create a project without providing a description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A boolean flag to enable auto deploy.
A boolean flag to enable automatic drift detection. Use this field to run a daily check to compare your configurations to your deployed resources to detect any difference.
The standard schema of a project.
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The cumulative list of needs attention items for a project. If the view is successfully retrieved, an empty or nonempty array is returned.
Possible values: 0 ≤ number of items ≤ 50
- CumulativeNeedsAttentionView
The event name.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
A unique ID for this individual event.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique ID for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version number of the configuration.
A value of
true
indicates that the fetch of the needs attention items failed. This property only exists if there was an error when you retrieved the cumulative needs attention view.The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The IBM Cloud location where a resource is deployed.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The resource group ID where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^[0-9a-zA-Z]+$/
The project status value.
Possible values: [
ready
,deleting
,deleting_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The resource group name where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The CRN of the Event Notifications instance if one is connected to this project.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^$|^crn:v[0-9](:([A-Za-z0-9\\-._~!$&'()*+,;=@\/]|%[0-9A-Z]{2})*){8}$/
The project configurations. These configurations are only included in the response of creating a project if a configuration array is specified in the request payload.
Possible values: 0 ≤ number of items ≤ 100
- Configs
A summary of a project configuration version.
- ApprovedVersion
A summary of the definition in a project configuration version.
- Definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A summary of a project configuration version.
- DeployedVersion
A summary of the definition in a project configuration version.
- Definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The description of a project configuration.
- Definition
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The project that is referenced by this resource.
- Project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- Definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]
The project environment. These environments are only included in the response if project environments were created on the project.
Possible values: 0 ≤ number of items ≤ 20
- Environments
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The project that is referenced by this resource.
- Project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- Definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment definition that is used in the project collection.
- Definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The definition of the project.
- Definition
The name of the project. It's unique within the account across regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The policy that indicates whether the resources are destroyed or not when a project is deleted.
A brief explanation of the project's use in the configuration of a deployable architecture. You can create a project without providing a description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A boolean flag to enable auto deploy.
A boolean flag to enable automatic drift detection. Use this field to run a daily check to compare your configurations to your deployed resources to detect any difference.
Status Code
The request was successful.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
A sample response for retrieving a project with configurations.
{ "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.service.url/v1/projects/cfbf901-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "acme-microservice", "description": "A microservice to deploy on top of ACME infrastructure.", "auto_deploy": false, "destroy_on_delete": true, "monitoring_enabled": false }, "configs": [ { "id": "673d79e4-52bf-4184-b8e9-d3ca3c110f96", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "common-variables", "description": "The common-variables configuration." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/673d79e4-52bf-4184-b8e9-d3ca3c110f96", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "modified_at": "2023-02-22T19:51:23.253Z", "update_available": false, "version": 1 }, { "id": "4a1d4ba2-54ba-43a7-975a-d82b5a7612d1", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "account-stage", "description": "The stage account configuration. The stage account hosts test environments prestage, performance, stage. This configuration configures services that are common to all these environments and regions. It's a `terraform_template` type of configuration that points to a GitHub repository that hosts the terraform modules that a Schematics workspace can deploy." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/4a1d4ba2-54ba-43a7-975a-d82b5a7612d1", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 }, { "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "env-stage", "description": "The stage environment configuration. It includes services that are common to all the environment regions. You must have a blueprint that configures all the services that are common to the stage regions. It's a `terraform_template` type of configuration that points to a GitHub repository that hosts the Terraform modules that a Schematics workspace can deploy." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/293c3c36-a094-4115-a12b-de0a9ca39be5", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 }, { "id": "596e8656-9d4b-41a5-8340-b0cbe8bd374a", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "region-us-south-stage", "description": "The stage `us-south` configuration. You must have a blueprint that configures the Virtual Private Cloud and Red Hat OpenShift stage `us-south`." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/596e8656-9d4b-41a5-8340-b0cbe8bd374a", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 }, { "id": "9c7afed6-17fb-4c56-a13d-440a78f936bd", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "region-eu-de-stage", "description": "The stage `eu-de` configuration. You must have a blueprint that configures the Virtual Private Cloud and Red Hat OpenShift stage `eu-de`." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/9c7afed6-17fb-4c56-a13d-440a78f936bd", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 } ], "environments": [ { "id": "b0c44146-1ef6-40c2-82ba-74d51149770a", "definition": { "name": "dev-environment", "description": "The development environment." }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "created_at": "2023-02-10T10:05:35.787Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/environments/b0c44146-1ef6-40c2-82ba-74d51149770a" } ], "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "cumulative_needs_attention_view": [ { "event": "project.instance.update" }, { "event_id": "489f0090-6d7c-4af5-8f20-9106543e4974" }, { "config_id": "069ab83e-5016-4bf2-bd50-cc95cf678293" }, { "config_version": 1 } ], "event_notifications_crn": "crn:v1:staging:public:event-notifications:us-south:a/06580c923e40314421d3b6cb40c01c68:instance-id::", "location": "us-south", "resource_group": "Default", "resource_group_id": "f37d2637ea814cfd9a1742683a713d24", "state": "ready" }
A sample response for retrieving a project with configurations.
{ "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.service.url/v1/projects/cfbf901-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "acme-microservice", "description": "A microservice to deploy on top of ACME infrastructure.", "auto_deploy": false, "destroy_on_delete": true, "monitoring_enabled": false }, "configs": [ { "id": "673d79e4-52bf-4184-b8e9-d3ca3c110f96", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "common-variables", "description": "The common-variables configuration." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/673d79e4-52bf-4184-b8e9-d3ca3c110f96", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "modified_at": "2023-02-22T19:51:23.253Z", "update_available": false, "version": 1 }, { "id": "4a1d4ba2-54ba-43a7-975a-d82b5a7612d1", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "account-stage", "description": "The stage account configuration. The stage account hosts test environments prestage, performance, stage. This configuration configures services that are common to all these environments and regions. It's a `terraform_template` type of configuration that points to a GitHub repository that hosts the terraform modules that a Schematics workspace can deploy." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/4a1d4ba2-54ba-43a7-975a-d82b5a7612d1", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 }, { "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "env-stage", "description": "The stage environment configuration. It includes services that are common to all the environment regions. You must have a blueprint that configures all the services that are common to the stage regions. It's a `terraform_template` type of configuration that points to a GitHub repository that hosts the Terraform modules that a Schematics workspace can deploy." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/293c3c36-a094-4115-a12b-de0a9ca39be5", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 }, { "id": "596e8656-9d4b-41a5-8340-b0cbe8bd374a", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "region-us-south-stage", "description": "The stage `us-south` configuration. You must have a blueprint that configures the Virtual Private Cloud and Red Hat OpenShift stage `us-south`." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/596e8656-9d4b-41a5-8340-b0cbe8bd374a", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 }, { "id": "9c7afed6-17fb-4c56-a13d-440a78f936bd", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "region-eu-de-stage", "description": "The stage `eu-de` configuration. You must have a blueprint that configures the Virtual Private Cloud and Red Hat OpenShift stage `eu-de`." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/9c7afed6-17fb-4c56-a13d-440a78f936bd", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 } ], "environments": [ { "id": "b0c44146-1ef6-40c2-82ba-74d51149770a", "definition": { "name": "dev-environment", "description": "The development environment." }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "created_at": "2023-02-10T10:05:35.787Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/environments/b0c44146-1ef6-40c2-82ba-74d51149770a" } ], "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "cumulative_needs_attention_view": [ { "event": "project.instance.update" }, { "event_id": "489f0090-6d7c-4af5-8f20-9106543e4974" }, { "config_id": "069ab83e-5016-4bf2-bd50-cc95cf678293" }, { "config_version": 1 } ], "event_notifications_crn": "crn:v1:staging:public:event-notifications:us-south:a/06580c923e40314421d3b6cb40c01c68:instance-id::", "location": "us-south", "resource_group": "Default", "resource_group_id": "f37d2637ea814cfd9a1742683a713d24", "state": "ready" }
Update a project
Update a project by specifying its ID.
Update a project by specifying its ID.
Update a project by specifying its ID.
Update a project by specifying its ID.
PATCH /v1/projects/{id}
update_project(
self,
id: str,
definition: 'ProjectPatchDefinitionBlock',
**kwargs,
) -> DetailedResponse
updateProject(params)
(project *ProjectV1) UpdateProject(updateProjectOptions *UpdateProjectOptions) (result *Project, response *core.DetailedResponse, err error)
(project *ProjectV1) UpdateProjectWithContext(ctx context.Context, updateProjectOptions *UpdateProjectOptions) (result *Project, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the UpdateProjectOptions
struct and set the fields to provide parameter values for the UpdateProject
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The request body of the new project definition document.
A project update example request.
{
"definition": {
"name": "acme-microservice",
"description": "A microservice to deploy on top of ACME infrastructure.",
"authorizations": {
"method": "trusted_profile",
"trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12"
}
}
}
The definition of the project.
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition of the project.
- definition
The name of the project. It's unique within the account across regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The policy that indicates whether the resources are destroyed or not when a project is deleted.
A boolean flag to enable auto deploy.
A brief explanation of the project's use in the configuration of a deployable architecture. You can create a project without providing a description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A boolean flag to enable automatic drift detection. Use this field to run a daily check to compare your configurations to your deployed resources to detect any difference.
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition of the project.
- definition
The name of the project. It's unique within the account across regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The policy that indicates whether the resources are destroyed or not when a project is deleted.
A boolean flag to enable auto deploy.
A brief explanation of the project's use in the configuration of a deployable architecture. You can create a project without providing a description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A boolean flag to enable automatic drift detection. Use this field to run a daily check to compare your configurations to your deployed resources to detect any difference.
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The UpdateProject options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition of the project.
Examples:{ "name": "acme-microservice", "description": "A microservice to deploy on top of ACME infrastructure.", "authorizations": { "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" } }
- Definition
The name of the project. It's unique within the account across regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The policy that indicates whether the resources are destroyed or not when a project is deleted.
A boolean flag to enable auto deploy.
A brief explanation of the project's use in the configuration of a deployable architecture. You can create a project without providing a description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A boolean flag to enable automatic drift detection. Use this field to run a daily check to compare your configurations to your deployed resources to detect any difference.
curl -X PATCH --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" --header "Content-Type: application/json" --data '{ "definition": { "name": "acme-microservice", "description": "A microservice to deploy on top of ACME infrastructure.", "authorizations": { "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" } } }' "{base_url}/v1/projects/{id}"
projectPatchDefinitionBlockModel := &projectv1.ProjectPatchDefinitionBlock{ Name: core.StringPtr("acme-microservice"), Description: core.StringPtr("A microservice to deploy on top of ACME infrastructure."), } updateProjectOptions := projectService.NewUpdateProjectOptions( projectIdLink, projectPatchDefinitionBlockModel, ) project, response, err := projectService.UpdateProject(updateProjectOptions) if err != nil { panic(err) } b, _ := json.MarshalIndent(project, "", " ") fmt.Println(string(b))
// Request models needed by this operation. // ProjectPatchDefinitionBlock const projectPatchDefinitionBlockModel = { name: 'acme-microservice', description: 'A microservice to deploy on top of ACME infrastructure.', }; const params = { id: projectIdLink, definition: projectPatchDefinitionBlockModel, }; let res; try { res = await projectService.updateProject(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
project_patch_definition_block_model = { 'name': 'acme-microservice', 'description': 'A microservice to deploy on top of ACME infrastructure.', } response = project_service.update_project( id=project_id_link, definition=project_patch_definition_block_model, ) project = response.get_result() print(json.dumps(project, indent=2))
Response
The standard schema of a project.
The project configurations. These configurations are only included in the response of creating a project if a configuration array is specified in the request payload.
Possible values: 0 ≤ number of items ≤ 100
The project environment. These environments are only included in the response if project environments were created on the project.
Possible values: 0 ≤ number of items ≤ 20
The definition of the project.
The resource group name where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
^(?!\s)(?!.*\s$)[^'"`<>{}\x00-\x1F]*$
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
(?!\s)(?!.*\s$)^(crn)[^'"`<>{}\s\x00-\x1F]*
Example:
crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The cumulative list of needs attention items for a project. If the view is successfully retrieved, an empty or nonempty array is returned.
Possible values: 0 ≤ number of items ≤ 50
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The IBM Cloud location where a resource is deployed.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
^(?!\s)(?!.*\s$)[^'"`<>{}\x00-\x1F]*$
The resource group ID where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
^[0-9a-zA-Z]+$
The project status value.
Possible values: [
ready
,deleting
,deleting_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(http(s)?:\/\/)[a-zA-Z0-9\$\-_\.+!\*'\(\),=&?\/]+$
The CRN of the Event Notifications instance if one is connected to this project.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
^$|^crn:v[0-9](:([A-Za-z0-9\-._~!$&'()*+,;=@/]|%[0-9A-Z]{2})*){8}$
A value of
true
indicates that the fetch of the needs attention items failed. This property only exists if there was an error when you retrieved the cumulative needs attention view.
The standard schema of a project.
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The cumulative list of needs attention items for a project. If the view is successfully retrieved, an empty or nonempty array is returned.
Possible values: 0 ≤ number of items ≤ 50
- cumulative_needs_attention_view
The event name.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
A unique ID for this individual event.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique ID for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version number of the configuration.
A value of
true
indicates that the fetch of the needs attention items failed. This property only exists if there was an error when you retrieved the cumulative needs attention view.The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The IBM Cloud location where a resource is deployed.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The resource group ID where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^[0-9a-zA-Z]+$/
The project status value.
Possible values: [
ready
,deleting
,deleting_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The resource group name where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The CRN of the Event Notifications instance if one is connected to this project.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^$|^crn:v[0-9](:([A-Za-z0-9\\-._~!$&'()*+,;=@\/]|%[0-9A-Z]{2})*){8}$/
The project configurations. These configurations are only included in the response of creating a project if a configuration array is specified in the request payload.
Possible values: 0 ≤ number of items ≤ 100
- configs
A summary of a project configuration version.
- approved_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A summary of a project configuration version.
- deployed_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The description of a project configuration.
- definition
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]
The project environment. These environments are only included in the response if project environments were created on the project.
Possible values: 0 ≤ number of items ≤ 20
- environments
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment definition that is used in the project collection.
- definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The definition of the project.
- definition
The name of the project. It's unique within the account across regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The policy that indicates whether the resources are destroyed or not when a project is deleted.
A brief explanation of the project's use in the configuration of a deployable architecture. You can create a project without providing a description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A boolean flag to enable auto deploy.
A boolean flag to enable automatic drift detection. Use this field to run a daily check to compare your configurations to your deployed resources to detect any difference.
The standard schema of a project.
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The cumulative list of needs attention items for a project. If the view is successfully retrieved, an empty or nonempty array is returned.
Possible values: 0 ≤ number of items ≤ 50
- cumulative_needs_attention_view
The event name.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
A unique ID for this individual event.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique ID for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version number of the configuration.
A value of
true
indicates that the fetch of the needs attention items failed. This property only exists if there was an error when you retrieved the cumulative needs attention view.The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The IBM Cloud location where a resource is deployed.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The resource group ID where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^[0-9a-zA-Z]+$/
The project status value.
Possible values: [
ready
,deleting
,deleting_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The resource group name where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The CRN of the Event Notifications instance if one is connected to this project.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^$|^crn:v[0-9](:([A-Za-z0-9\\-._~!$&'()*+,;=@\/]|%[0-9A-Z]{2})*){8}$/
The project configurations. These configurations are only included in the response of creating a project if a configuration array is specified in the request payload.
Possible values: 0 ≤ number of items ≤ 100
- configs
A summary of a project configuration version.
- approved_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A summary of a project configuration version.
- deployed_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The description of a project configuration.
- definition
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]
The project environment. These environments are only included in the response if project environments were created on the project.
Possible values: 0 ≤ number of items ≤ 20
- environments
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment definition that is used in the project collection.
- definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The definition of the project.
- definition
The name of the project. It's unique within the account across regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The policy that indicates whether the resources are destroyed or not when a project is deleted.
A brief explanation of the project's use in the configuration of a deployable architecture. You can create a project without providing a description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A boolean flag to enable auto deploy.
A boolean flag to enable automatic drift detection. Use this field to run a daily check to compare your configurations to your deployed resources to detect any difference.
The standard schema of a project.
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The cumulative list of needs attention items for a project. If the view is successfully retrieved, an empty or nonempty array is returned.
Possible values: 0 ≤ number of items ≤ 50
- CumulativeNeedsAttentionView
The event name.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
A unique ID for this individual event.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique ID for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version number of the configuration.
A value of
true
indicates that the fetch of the needs attention items failed. This property only exists if there was an error when you retrieved the cumulative needs attention view.The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The IBM Cloud location where a resource is deployed.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The resource group ID where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^[0-9a-zA-Z]+$/
The project status value.
Possible values: [
ready
,deleting
,deleting_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The resource group name where the project's data and tools are created.
Possible values: 0 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The CRN of the Event Notifications instance if one is connected to this project.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^$|^crn:v[0-9](:([A-Za-z0-9\\-._~!$&'()*+,;=@\/]|%[0-9A-Z]{2})*){8}$/
The project configurations. These configurations are only included in the response of creating a project if a configuration array is specified in the request payload.
Possible values: 0 ≤ number of items ≤ 100
- Configs
A summary of a project configuration version.
- ApprovedVersion
A summary of the definition in a project configuration version.
- Definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A summary of a project configuration version.
- DeployedVersion
A summary of the definition in a project configuration version.
- Definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The description of a project configuration.
- Definition
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The project that is referenced by this resource.
- Project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- Definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]
The project environment. These environments are only included in the response if project environments were created on the project.
Possible values: 0 ≤ number of items ≤ 20
- Environments
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The project that is referenced by this resource.
- Project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- Definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment definition that is used in the project collection.
- Definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The definition of the project.
- Definition
The name of the project. It's unique within the account across regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The policy that indicates whether the resources are destroyed or not when a project is deleted.
A brief explanation of the project's use in the configuration of a deployable architecture. You can create a project without providing a description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A boolean flag to enable auto deploy.
A boolean flag to enable automatic drift detection. Use this field to run a daily check to compare your configurations to your deployed resources to detect any difference.
Status Code
The request was successful.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
A sample response for retrieving a project with configurations.
{ "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.service.url/v1/projects/cfbf901-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "acme-microservice", "description": "A microservice to deploy on top of ACME infrastructure.", "auto_deploy": false, "destroy_on_delete": true, "monitoring_enabled": false }, "configs": [ { "id": "673d79e4-52bf-4184-b8e9-d3ca3c110f96", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "common-variables", "description": "The common-variables configuration." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/673d79e4-52bf-4184-b8e9-d3ca3c110f96", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "modified_at": "2023-02-22T19:51:23.253Z", "update_available": false, "version": 1 }, { "id": "4a1d4ba2-54ba-43a7-975a-d82b5a7612d1", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "account-stage", "description": "The stage account configuration. The stage account hosts test environments prestage, performance, stage. This configuration configures services that are common to all these environments and regions. It's a `terraform_template` type of configuration that points to a GitHub repository that hosts the terraform modules that a Schematics workspace can deploy." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/4a1d4ba2-54ba-43a7-975a-d82b5a7612d1", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 }, { "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "env-stage", "description": "The stage environment configuration. It includes services that are common to all the environment regions. You must have a blueprint that configures all the services that are common to the stage regions. It's a `terraform_template` type of configuration that points to a GitHub repository that hosts the Terraform modules that a Schematics workspace can deploy." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/293c3c36-a094-4115-a12b-de0a9ca39be5", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 }, { "id": "596e8656-9d4b-41a5-8340-b0cbe8bd374a", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "region-us-south-stage", "description": "The stage `us-south` configuration. You must have a blueprint that configures the Virtual Private Cloud and Red Hat OpenShift stage `us-south`." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/596e8656-9d4b-41a5-8340-b0cbe8bd374a", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 }, { "id": "9c7afed6-17fb-4c56-a13d-440a78f936bd", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "region-eu-de-stage", "description": "The stage `eu-de` configuration. You must have a blueprint that configures the Virtual Private Cloud and Red Hat OpenShift stage `eu-de`." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/9c7afed6-17fb-4c56-a13d-440a78f936bd", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 } ], "environments": [ { "id": "b0c44146-1ef6-40c2-82ba-74d51149770a", "definition": { "name": "dev-environment", "description": "The development environment." }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "created_at": "2023-02-10T10:05:35.787Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/environments/b0c44146-1ef6-40c2-82ba-74d51149770a" } ], "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "cumulative_needs_attention_view": [ { "event": "project.instance.update" }, { "event_id": "489f0090-6d7c-4af5-8f20-9106543e4974" }, { "config_id": "069ab83e-5016-4bf2-bd50-cc95cf678293" }, { "config_version": 1 } ], "event_notifications_crn": "crn:v1:staging:public:event-notifications:us-south:a/06580c923e40314421d3b6cb40c01c68:instance-id::", "location": "us-south", "resource_group": "Default", "resource_group_id": "f37d2637ea814cfd9a1742683a713d24", "state": "ready" }
A sample response for retrieving a project with configurations.
{ "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.service.url/v1/projects/cfbf901-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "acme-microservice", "description": "A microservice to deploy on top of ACME infrastructure.", "auto_deploy": false, "destroy_on_delete": true, "monitoring_enabled": false }, "configs": [ { "id": "673d79e4-52bf-4184-b8e9-d3ca3c110f96", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "common-variables", "description": "The common-variables configuration." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/673d79e4-52bf-4184-b8e9-d3ca3c110f96", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "modified_at": "2023-02-22T19:51:23.253Z", "update_available": false, "version": 1 }, { "id": "4a1d4ba2-54ba-43a7-975a-d82b5a7612d1", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "account-stage", "description": "The stage account configuration. The stage account hosts test environments prestage, performance, stage. This configuration configures services that are common to all these environments and regions. It's a `terraform_template` type of configuration that points to a GitHub repository that hosts the terraform modules that a Schematics workspace can deploy." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/4a1d4ba2-54ba-43a7-975a-d82b5a7612d1", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 }, { "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "env-stage", "description": "The stage environment configuration. It includes services that are common to all the environment regions. You must have a blueprint that configures all the services that are common to the stage regions. It's a `terraform_template` type of configuration that points to a GitHub repository that hosts the Terraform modules that a Schematics workspace can deploy." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/293c3c36-a094-4115-a12b-de0a9ca39be5", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 }, { "id": "596e8656-9d4b-41a5-8340-b0cbe8bd374a", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "region-us-south-stage", "description": "The stage `us-south` configuration. You must have a blueprint that configures the Virtual Private Cloud and Red Hat OpenShift stage `us-south`." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/596e8656-9d4b-41a5-8340-b0cbe8bd374a", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 }, { "id": "9c7afed6-17fb-4c56-a13d-440a78f936bd", "created_at": "2023-02-22T19:51:23.253Z", "definition": { "name": "region-eu-de-stage", "description": "The stage `eu-de` configuration. You must have a blueprint that configures the Virtual Private Cloud and Red Hat OpenShift stage `eu-de`." }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/9c7afed6-17fb-4c56-a13d-440a78f936bd", "is_draft": true, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "state": "draft", "update_available": false, "modified_at": "2023-02-22T19:51:23.253Z", "version": 1 } ], "environments": [ { "id": "b0c44146-1ef6-40c2-82ba-74d51149770a", "definition": { "name": "dev-environment", "description": "The development environment." }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "created_at": "2023-02-10T10:05:35.787Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/environments/b0c44146-1ef6-40c2-82ba-74d51149770a" } ], "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "cumulative_needs_attention_view": [ { "event": "project.instance.update" }, { "event_id": "489f0090-6d7c-4af5-8f20-9106543e4974" }, { "config_id": "069ab83e-5016-4bf2-bd50-cc95cf678293" }, { "config_version": 1 } ], "event_notifications_crn": "crn:v1:staging:public:event-notifications:us-south:a/06580c923e40314421d3b6cb40c01c68:instance-id::", "location": "us-south", "resource_group": "Default", "resource_group_id": "f37d2637ea814cfd9a1742683a713d24", "state": "ready" }
Delete a project
Delete a project document by specifying the ID. A project can be deleted only after you delete all of its resources.
Delete a project document by specifying the ID. A project can be deleted only after you delete all of its resources.
Delete a project document by specifying the ID. A project can be deleted only after you delete all of its resources.
Delete a project document by specifying the ID. A project can be deleted only after you delete all of its resources.
DELETE /v1/projects/{id}
delete_project(
self,
id: str,
**kwargs,
) -> DetailedResponse
deleteProject(params)
(project *ProjectV1) DeleteProject(deleteProjectOptions *DeleteProjectOptions) (result *ProjectDeleteResponse, response *core.DetailedResponse, err error)
(project *ProjectV1) DeleteProjectWithContext(ctx context.Context, deleteProjectOptions *DeleteProjectOptions) (result *ProjectDeleteResponse, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the DeleteProjectOptions
struct and set the fields to provide parameter values for the DeleteProject
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The DeleteProject options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
curl -X DELETE --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" "{base_url}/v1/projects/{id}"
deleteProjectOptions := projectService.NewDeleteProjectOptions( projectIdLink, ) projectDeleteResponse, response, err := projectService.DeleteProject(deleteProjectOptions) if err != nil { panic(err) } b, _ := json.MarshalIndent(projectDeleteResponse, "", " ") fmt.Println(string(b))
const params = { id: projectIdLink, }; let res; try { res = await projectService.deleteProject(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
response = project_service.delete_project( id=project_id_link, ) project_delete_response = response.get_result() print(json.dumps(project_delete_response, indent=2))
Response
The ID of the deleted project.
The ID of the deleted project or configuration.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The ID of the deleted project.
The ID of the deleted project or configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The ID of the deleted project.
The ID of the deleted project or configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The ID of the deleted project.
The ID of the deleted project or configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
Status Code
The server successfully accepted the request to process the resource.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The project cannot be deleted. You're receiving this response because at least one of the configurations is in an active pipeline state (validating/deploying/undeploying). Wait for these pipeline actions to end before you run the deletion again.
The example response to a request to delete a project.
{ "id": "4059955c-ccb3-4fd3-aa48-34e3b8334f80" }
The example response to a request to delete a project.
{ "id": "4059955c-ccb3-4fd3-aa48-34e3b8334f80" }
Sync a project
Sync a project.
POST /v1/projects/{id}/sync
Authentication
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Response
Status Code
The request was successful but the response is empty.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The request cannot be processed because of a conflict between the request and the current client-controlled state in the system.
No Sample Response
Get project spending
The spending data on a project
POST /v1/projects/{project_id}/spending
Authentication
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Query Parameters
The last entry that is returned on the page. The server uses this parameter to determine the first entry that is returned on the next page. If this parameter is not specified, the logical first page is returned.
Possible values: 0 ≤ length ≤ 1536, Value must match regular expression
^$|^(?!\s)(?!.*\s$)[^\x00-\x1F]*$
Default:
The maximum number of resources to return. The number of resources that are returned is the same, except for the last page.
Possible values: 1 ≤ value ≤ 100
Default:
10
Data to create a specified report
The month being searched for usage data (optional)
Possible values: 0 ≤ number of items ≤ 12, length = 7, Value must match regular expression
^[\.\-0-9]+$
The scope fo the search for usage data
Allowable values: [
configs
,da
,config
,env
]The ID of the config being searched for usage data (if using the 'config' scope)
Possible values: 0 ≤ length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Response
The spending details on a project
The collection list operation response schema that should define the array property with the name "configs".
Possible values: 0 ≤ number of items ≤ 200
A pagination token.
Possible values: 0 ≤ length ≤ 1536, Value must match regular expression
^$|^(?!\s)(?!.*\s$)[^\x00-\x1F]*$
A pagination link.
A pagination link.
Status Code
Success
Bad Request
Sample spending API response.
{ "configs": [ { "config_id": "some-config-id", "config_name": "config-1", "usage": [ { "month": "2024-03", "limit": 30, "count": 4, "first": { "href": "/v4/accounts/some-account-id/resource_instances/usage/2024-03?_limit=30&_names=false&_tags=true" }, "next": { "href": "/v4/accounts/some-account-id/resource_instances/usage/2024-03?_limit=30&_names=false&_start=some-long-start-string&_names=false&_tags=true", "offset": "some-offset-string" }, "resources": [ { "account_id": "some-account-id", "resource_instance_id": "crn:v1:staging:public:continuous-delivery:us-south:a/some-account-id:some-instance-id::", "resource_group_id": "some-resource-group-id", "month": "2024-03", "pricing_country": "USA", "billing_country": "USA", "currency_code": "USD", "plan_id": "some-plan-id", "resource_id": "some-resource-id", "billable": true, "pricing_plan_id": "billable:v4:some-plan-id::some-pricing-id:", "region": "us-south", "usage": [ { "metric": "AUTHORIZED_USERS_PER_MONTH", "unit": "Authorized User", "price": [ { "unitQuantity": "1", "tier_model": "Granular Tier", "price": 37.7, "quantity_tier": "1" } ], "additional_properties": null, "quantity": 0.3870967741935484, "cost": 14.580414193548387, "rated_cost": 14.593548387096774, "rateable_quantity": 0.3870967741935484, "discounts": [ { "name": "platform discount", "display_name": "platform discount", "ref": "discount-some-discount-id", "discount": 0.09 } ] } ], "currency_rate": 1, "tags": null, "service_tags": [ "project::config_id:some-config-id", "project::project_id:some-project-id" ] } ] } ] } ], "token": "some-token-string", "first": { "href": "https://projects.api.test.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/spending?limit=10" }, "next": { "href": "https://projects.api.test.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/spending?limit=10&start=some-offset-string" } }
Resolve project references
Resolve project references.
POST /v1/resolve
Authentication
Request
A batch of one or more references.
The example of a request for a collection of project batch references.
{
"references": [
{
"reference": "ref://project.myproject/configs/myconfig/inputs/region"
},
{
"reference": "ref:./inputs/region",
"context": "ref://project.myproject/configs/myconfig/"
}
]
}
The references of the batch request.
Possible values: 0 ≤ number of items ≤ 10000
Response
The resolved batch reference collection.
The unique correlation UUID for the request.
Possible values: length ≤ 128, Value must match regular expression
^[\-0-9a-zA-Z]+$
The resolved batch reference collection.
Possible values: 0 ≤ number of items ≤ 10000
Status Code
You successfully resolved project references.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The example of a resolved project batch reference collection.
{ "correlation_id": "3cd535c7-04a9-4198-a550-8b7737bf748a", "references": [ { "reference": "ref://project.myproject/configs/myconfig/inputs/region", "state": "The project reference was resolved.", "code": 200, "request_id": "66c535c7-03a0-6144-b340-8e5737bf688c", "value": "us-south", "content_type": "text/plain" }, { "reference": "ref:./inputs/region", "context": "ref://project.myproject/configs/myconfig/", "state": "The project reference was resolved.", "code": 200, "request_id": "66c535c7-03a0-6144-b340-8e5737bf688c", "value": "us-south", "content_type": "text/plain" }, { "reference": "ref:./inputs/regionx", "context": "ref://project.myproject/configs/myconfig/", "state": "The project reference ref://project.myproject/configs/myconfig/inputs/regionx is invalid", "state_code": "INVALID_PROJECT_REFERENCE_ERROR", "code": 400, "request_id": "66c535c7-03a0-6144-b340-8e5737bf688c" } ] }
List allowed locations for project creation
Returns list of allowed locations that caller is allowed to create projects from.
GET /v1/locations
Authentication
Response
Response containing locations user is allowed to create projects from.
The collection of locations in which projects can be created.
Possible values: 0 ≤ number of items ≤ 50
Status Code
The request was successful.
The credentials are invalid or authentication is required to succeed.
The request was not completed by the server. It could be due to an internal error or in some cases, invalid data in the request.
The sample response for retrieving the allowed project locations for project creation.
{ "locations": [ { "location": "us-south", "location_display_name": "Dallas" }, { "location": "us-east", "location_display_name": "Washington DC" }, { "location": "eu-de", "location_display_name": "Frankfurt" }, { "location": "eu-gb", "location_display_name": "London" }, { "location": "ca-tor", "location_display_name": "Toronto" } ] }
List project resources
List resources that have been added to a project.
GET /v1/projects/{id}/resources
Authentication
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Query Parameters
The last entry that is returned on the page. The server uses this parameter to determine the first entry that is returned on the next page. If this parameter is not specified, the logical first page is returned.
Possible values: 0 ≤ length ≤ 1536, Value must match regular expression
^$|^(?!\s)(?!.*\s$)[^\x00-\x1F]*$
Default:
The maximum number of resources to return. The number of resources that are returned is the same, except for the last page.
Possible values: 1 ≤ value ≤ 100
Default:
10
An optional string indicating what type of resources are to be included in the search results.
Allowable values: [
user_deployed
,project_deployed
,all
]The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Response
The project resource list.
The collection list operation response schema that defines the array property with the name
resources
.Possible values: 0 ≤ number of items ≤ 100
A pagination limit.
Possible values: 1 ≤ value ≤ 100
A pagination token.
Possible values: 0 ≤ length ≤ 1536, Value must match regular expression
^$|^(?!\s)(?!.*\s$)[^\x00-\x1F]*$
A pagination link.
A pagination link.
Status Code
You successfully retrieved the resources added to the project.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
The example response to a request to get project resources.
{ "resources": [ { "resource_crn": "crn:v1:staging:public:toolchain:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::", "resource_name": "toolchain_instance", "account_id": "499b176abb3e1c9727df87ae48b27c7b", "location": "us-south", "resource_type": "user_deployed", "resource_status": "active", "resource_group_id": "5201af285aba49fa97c31ad44967010f", "tags": [], "service_tags": [ "project::project_id:cfbf9050-ab8e-ac97-b01b-ab5af830be8a" ], "project_id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "terraform_type": "ibm_cd_toolchain", "resource_group_name": "Default" }, { "resource_crn": "crn:v1:staging:public:cloud-object-storage:global:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::", "resource_name": "cos_bucket_instance", "account_id": "499b176abb3e1c9727df87ae48b27c7b", "location": "us-south", "resource_type": "project_deployed", "resource_status": "active", "resource_group_id": "3201af285aba49fa97c31ad44967010f", "tags": [], "service_tags": [ "project::project_id:cfbf9050-ab8e-ac97-b01b-ab5af830be8a" ], "project_id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "terraform_type": "ibm_cos_bucket", "resource_group_name": "Default" } ], "token": "eyJhY2NvdW50SWQiOiIqIiwidXNlcklk", "limit": 10, "first": { "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/resources" }, "next": { "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/resources?&start=eyJhY2NvdW50SWQiOiIqIiwidXNlcklk" } }
Updates the resources in a project
Updates the resources in a project using a collection of JSON patch-like operations.
POST /v1/projects/{id}/resources
Authentication
Request
Custom Headers
The IBM trusted profile ID
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
^(?!\s)(?!.*\s$)[^`<>\x00-\x1F]*$
The IBM Cloud API key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
^(?!\s)(?!.*\s$)[^`<>\x00-\x1F]*$
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The request body for the change delta of the project resources to update.
The example request to update project resources.
{
"resources": [
{
"op": "add",
"value": {
"resource_crn": "crn:v1:staging:public:toolchain:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::"
}
},
{
"op": "remove",
"value": {
"resource_crn": "crn:v1:staging:public:cloud-object-storage:global:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::"
}
}
]
}
The collection list response schema that defines the array property with the name
resources
.Possible values: 0 ≤ number of items ≤ 100
Response
The project resources update response.
The resource operations that were successfully executed.
Possible values: 0 ≤ number of items ≤ 100
If errors occurred while executing any resource operations, those errors will be included here.
Possible values: 0 ≤ number of items ≤ 100
A lowercase UUID that uniquely identifies the request.
The status code that is used for the response.
Status Code
Some or all of the resource operations were successfully executed.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
An example response from updating project resources.
{ "resources": [ { "op": "add", "value": { "resource_crn": "crn:v1:staging:public:toolchain:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-a6d576183bb2::" } } ], "errors": [ { "code": "not_found", "message": "The resource with CRN crn:v1:staging:public:toolchain:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb3::' could not be found in the account with ID a94cbc051abd47828a396c94adaba9c1." }, { "code": "bad_request", "message": "The resource with CRN crn:v1:staging:public:toolchain:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb8::' was added to another project. A resource can be added only to a single project." } ], "status_code": 200 }
List all project available resources
Lists resources in an account that are available to add to the project. The account is specified using a trusted profile or API key.
GET /v1/projects/{id}/available_resources
Authentication
Request
Custom Headers
The IBM trusted profile ID
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
^(?!\s)(?!.*\s$)[^`<>\x00-\x1F]*$
The IBM Cloud API key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
^(?!\s)(?!.*\s$)[^`<>\x00-\x1F]*$
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Query Parameters
The last entry that is returned on the page. The server uses this parameter to determine the first entry that is returned on the next page. If this parameter is not specified, the logical first page is returned.
Possible values: 0 ≤ length ≤ 1536, Value must match regular expression
^$|^(?!\s)(?!.*\s$)[^\x00-\x1F]*$
Default:
The maximum number of resources to return. The number of resources that are returned is the same, except for the last page.
Possible values: 1 ≤ value ≤ 100
Default:
10
Response
The project resource list.
The collection list operation response schema that defines the array property with the name
resources
.Possible values: 0 ≤ number of items ≤ 100
A pagination limit.
Possible values: 1 ≤ value ≤ 100
A pagination token.
Possible values: 0 ≤ length ≤ 1536, Value must match regular expression
^$|^(?!\s)(?!.*\s$)[^\x00-\x1F]*$
A pagination link.
A pagination link.
Status Code
You successfully retrieved the resources.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
The example response to a request to get project resources.
{ "resources": [ { "resource_crn": "crn:v1:staging:public:toolchain:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::", "resource_name": "toolchain_instance", "account_id": "499b176abb3e1c9727df87ae48b27c7b", "location": "us-south", "resource_type": "user_deployed", "resource_status": "active", "resource_group_id": "5201af285aba49fa97c31ad44967010f", "tags": [], "service_tags": [ "project::project_id:cfbf9050-ab8e-ac97-b01b-ab5af830be8a" ], "project_id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "terraform_type": "ibm_cd_toolchain", "resource_group_name": "Default" }, { "resource_crn": "crn:v1:staging:public:cloud-object-storage:global:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::", "resource_name": "cos_bucket_instance", "account_id": "499b176abb3e1c9727df87ae48b27c7b", "location": "us-south", "resource_type": "project_deployed", "resource_status": "active", "resource_group_id": "3201af285aba49fa97c31ad44967010f", "tags": [], "service_tags": [ "project::project_id:cfbf9050-ab8e-ac97-b01b-ab5af830be8a" ], "project_id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "terraform_type": "ibm_cos_bucket", "resource_group_name": "Default" } ], "token": "eyJhY2NvdW50SWQiOiIqIiwidXNlcklk", "limit": 10, "first": { "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/resources" }, "next": { "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/resources?&start=eyJhY2NvdW50SWQiOiIqIiwidXNlcklk" } }
Get project resources for an account
Get the project resources for an account, as returned by Schematics. This information is used by the GhoST service.
GET /v1/projects_resources
Authentication
Request
Query Parameters
The IBM Cloud account id of the account owning the resource.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
^(?!\s)(?!.*\s$).*$
The last entry that is returned on the page. The server uses this parameter to determine the first entry that is returned on the next page. If this parameter is not specified, the logical first page is returned.
Possible values: 0 ≤ length ≤ 1536, Value must match regular expression
^$|^(?!\s)(?!.*\s$)[^\x00-\x1F]*$
Default:
The maximum number of resources to return. The number of resources that are returned is the same, except for the last page.
Possible values: 1 ≤ value ≤ 100
Default:
10
Response
The project resources returned by Schematics
The collection list operation response schema that should define the array property with the name "configs".
Possible values: 0 ≤ number of items ≤ 1000
A pagination limit.
Possible values: 1 ≤ value ≤ 100
A pagination link.
A pagination link.
Status Code
You successfully retrieved the resources.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
An example response from project resources for an account.
{ "limit": 10, "first": { "href": "https://projects.api.cloud.ibm.com/v1/projects_resources?account_id=e8bb1d11250e14b0de3dfa9f42a60e00" }, "next": { "href": "https://projects.api.cloud.ibm.com/v1/projects_resources?account_id=e8bb1d11250e14b0de3dfa9f42a60e00&limit=100&start=6860801d-994a-497f-8b51-9166cae1c8ff" }, "projects": [ { "id": "6860801d-994a-497f-8b51-9166cae1c8ff", "resources": [ { "project_id": "6860801d-994a-497f-8b51-9166cae1c8ff", "config_id": "1d70615f-387c-4325-af7c-a2067dc042fa", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.26e5e9c0-745d-4e5a-ad5a-08bc0a374b5a-global", "crn": "crn:v1:bluemix:public:cloud-object-storage:global:a/e8bb1d11250e14b0de3dfa9f42a60e00:503c8368-9953-4695-b1ff-7e30f32cdb7f:bucket:sample-solution-app", "crn_type": "ibm", "id": "cos_bucket_instance_id", "name": "cos_bucket_instance", "type": "ibm_cos_bucket" } ] } ] }
Get project resources for a single project
Get the project resources for a single project, as returned by Schematics. This information is used by the GhoST service.
GET /v1/projects_resources/{id}/resources
Authentication
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Response
The project resources returned by Schematics
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The project resources returned by Schematics
Possible values: 0 ≤ number of items ≤ 1000
Status Code
You successfully retrieved the resources.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
An example response from getting resources for a project.
{ "id": "6860801d-994a-497f-8b51-9166cae1c8ff", "resources": [ { "project_id": "6860801d-994a-497f-8b51-9166cae1c8ff", "config_id": "1d70615f-387c-4325-af7c-a2067dc042fa", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.26e5e9c0-745d-4e5a-ad5a-08bc0a374b5a-global", "crn": "crn:v1:bluemix:public:cloud-object-storage:global:a/e8bb1d11250e14b0de3dfa9f42a60e00:503c8368-9953-4695-b1ff-7e30f32cdb7f::", "crn_type": "ibm", "id": "cos_instance_id", "name": "cos_instance", "type": "ibm_cos" }, { "project_id": "6860801d-994a-497f-8b51-9166cae1c8ff", "config_id": "1d70615f-387c-4325-af7c-a2067dc042fa", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.26e5e9c0-745d-4e5a-ad5a-08bc0a374b5a-global", "crn": "crn:v1:bluemix:public:cloud-object-storage:global:a/e8bb1d11250e14b0de3dfa9f42a60e00:503c8368-9953-4695-b1ff-7e30f32cdb7f:bucket:sample-solution-app", "crn_type": "ibm", "id": "cos_bucket_instance_id", "name": "cos_bucket_instance", "type": "ibm_cos_bucket" } ] }
Get project resource detail
Get the project resource detail, as returned by Schematics. This information is used by the GhoST service.
GET /v1/projects_resources/{id}/resources/{resource_crn}
Authentication
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The CRN of the resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
(?!\s)(?!.*\s$)^(crn)[^'"`<>{}\s\x00-\x1F]*
Example:
crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
Response
The project resource returned by Schematics
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The project resource returned by Schematics
Possible values: number of items = 1
Status Code
You successfully retrieved the resource.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
An example response from getting detail for a project resource.
{ "id": "6860801d-994a-497f-8b51-9166cae1c8ff", "resources": [ { "project_id": "6860801d-994a-497f-8b51-9166cae1c8ff", "config_id": "1d70615f-387c-4325-af7c-a2067dc042fa", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.26e5e9c0-745d-4e5a-ad5a-08bc0a374b5a-global", "crn": "crn:v1:bluemix:public:cloud-object-storage:global:a/e8bb1d11250e14b0de3dfa9f42a60e00:503c8368-9953-4695-b1ff-7e30f32cdb7f:bucket:sample-solution-app", "crn_type": "ibm", "id": "cos_bucket_instance_id", "name": "cos_bucket_instance", "type": "ibm_cos_bucket" } ] }
Create an environment
Create an environment to group related configurations together and share values across them for easier deployment. For more information, see Creating an environment.
Create an environment to group related configurations together and share values across them for easier deployment. For more information, see Creating an environment.
Create an environment to group related configurations together and share values across them for easier deployment. For more information, see Creating an environment.
Create an environment to group related configurations together and share values across them for easier deployment. For more information, see Creating an environment.
POST /v1/projects/{project_id}/environments
create_project_environment(
self,
project_id: str,
definition: 'EnvironmentDefinitionRequiredProperties',
**kwargs,
) -> DetailedResponse
createProjectEnvironment(params)
(project *ProjectV1) CreateProjectEnvironment(createProjectEnvironmentOptions *CreateProjectEnvironmentOptions) (result *Environment, response *core.DetailedResponse, err error)
(project *ProjectV1) CreateProjectEnvironmentWithContext(ctx context.Context, createProjectEnvironmentOptions *CreateProjectEnvironmentOptions) (result *Environment, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the CreateProjectEnvironmentOptions
struct and set the fields to provide parameter values for the CreateProjectEnvironment
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The request body for a valid environment document.
A sample environment update request.
{
"definition": {
"name": "development",
"description": "The environment development.",
"authorizations": {
"method": "trusted_profile",
"trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12"
},
"inputs": {
"resource_group": "stage",
"region": "us-south"
},
"compliance_profile": {
"id": "some-profile-id",
"instance_id": "some-instance-id",
"instance_location": "us-south",
"profile_name": "some-profile-name",
"attachment_id": "some-attachment-id"
}
}
}
The environment definition.
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The environment definition.
- definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Allowable values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Allowable values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The environment definition.
- definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Allowable values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Allowable values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The CreateProjectEnvironment options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The environment definition.
Examples:{ "name": "development", "description": "The environment development.", "authorizations": { "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }, "inputs": { "resource_group": "stage", "region": "us-south" }, "compliance_profile": { "id": "some-profile-id", "instance_id": "some-instance-id", "instance_location": "us-south", "profile_name": "some-profile-name", "attachment_id": "some-attachment-id" } }
- Definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- Authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Allowable values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- ComplianceProfile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Allowable values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
curl -X POST --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" --header "Content-Type: application/json" --data '{ "definition": { "name": "development", "description": "The environment development.", "authorizations": { "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }, "inputs": { "resource_group": "stage", "region": "us-south" }, "compliance_profile": { "id": "some-profile-id", "instance_id": "some-instance-id", "instance_location": "us-south", "profile_name": "some-profile-name", "attachment_id": "some-attachment-id" } } }' "{base_url}/v1/projects/{project_id}/environments"
projectConfigAuthModel := &projectv1.ProjectConfigAuth{ TrustedProfileID: core.StringPtr("Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12"), Method: core.StringPtr("trusted_profile"), } projectComplianceProfileModel := &projectv1.ProjectComplianceProfile{ ID: core.StringPtr("some-profile-id"), InstanceID: core.StringPtr("some-instance-id"), InstanceLocation: core.StringPtr("us-south"), AttachmentID: core.StringPtr("some-attachment-id"), ProfileName: core.StringPtr("some-profile-name"), } environmentDefinitionRequiredPropertiesModel := &projectv1.EnvironmentDefinitionRequiredProperties{ Description: core.StringPtr("The environment development."), Name: core.StringPtr("development"), Authorizations: projectConfigAuthModel, ComplianceProfile: projectComplianceProfileModel, } createProjectEnvironmentOptions := projectService.NewCreateProjectEnvironmentOptions( projectIdLink, environmentDefinitionRequiredPropertiesModel, ) environment, response, err := projectService.CreateProjectEnvironment(createProjectEnvironmentOptions) if err != nil { panic(err) } b, _ := json.MarshalIndent(environment, "", " ") fmt.Println(string(b))
// Request models needed by this operation. // ProjectConfigAuth const projectConfigAuthModel = { trusted_profile_id: 'Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12', method: 'trusted_profile', }; // ProjectComplianceProfile const projectComplianceProfileModel = { id: 'some-profile-id', instance_id: 'some-instance-id', instance_location: 'us-south', attachment_id: 'some-attachment-id', profile_name: 'some-profile-name', }; // EnvironmentDefinitionRequiredProperties const environmentDefinitionRequiredPropertiesModel = { description: 'The environment development.', name: 'development', authorizations: projectConfigAuthModel, inputs: { resource_group: 'stage', region: 'us-south' }, compliance_profile: projectComplianceProfileModel, }; const params = { projectId: projectIdLink, definition: environmentDefinitionRequiredPropertiesModel, }; let res; try { res = await projectService.createProjectEnvironment(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
project_config_auth_model = { 'trusted_profile_id': 'Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12', 'method': 'trusted_profile', } project_compliance_profile_model = { 'id': 'some-profile-id', 'instance_id': 'some-instance-id', 'instance_location': 'us-south', 'attachment_id': 'some-attachment-id', 'profile_name': 'some-profile-name', } environment_definition_required_properties_model = { 'description': 'The environment development.', 'name': 'development', 'authorizations': project_config_auth_model, 'inputs': {'resource_group': 'stage', 'region': 'us-south'}, 'compliance_profile': project_compliance_profile_model, } response = project_service.create_project_environment( project_id=project_id_link, definition=environment_definition_required_properties_model, ) environment = response.get_result() print(json.dumps(environment, indent=2))
Response
The definition of a project environment.
The environment definition.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(http(s)?:\/\/)[a-zA-Z0-9\$\-_\.+!\*'\(\),=&?\/]+$
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(?!\s)(?!.*\s$).+$
The project that is referenced by this resource.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The target account ID derived from the authentication block values. The target account exists only if the environment currently has an authorization block.
Possible values: length ≤ 64, Value must match regular expression
^[a-zA-Z0-9.-]+$
The definition of a project environment.
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The target account ID derived from the authentication block values. The target account exists only if the environment currently has an authorization block.
Possible values: length ≤ 64, Value must match regular expression
/^[a-zA-Z0-9.-]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment definition.
- definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The definition of a project environment.
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The target account ID derived from the authentication block values. The target account exists only if the environment currently has an authorization block.
Possible values: length ≤ 64, Value must match regular expression
/^[a-zA-Z0-9.-]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment definition.
- definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The definition of a project environment.
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The project that is referenced by this resource.
- Project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- Definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The target account ID derived from the authentication block values. The target account exists only if the environment currently has an authorization block.
Possible values: length ≤ 64, Value must match regular expression
/^[a-zA-Z0-9.-]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment definition.
- Definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- Authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- ComplianceProfile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
Status Code
The new resource was created.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The sample environment response.
{ "id": "env123", "definition": { "name": "development", "description": "The environment development.", "authorizations": { "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }, "inputs": { "resource_group": "stage", "region": "us-south" }, "compliance_profile": { "id": "some-profile-id", "instance_id": "some-instance-id", "instance_location": "us-south", "profile_name": "some-profile-name", "attachment_id": "some-attachment-id" } }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "created_at": "2023-06-29T03:28:14.709Z", "modified_at": "2023-06-29T03:28:14.709Z", "href": "https://projects.api.test.cloud.ibm.com/v1/projects/6fd53106-7ce6-429e-8c57-f22e832d0c4b/environments/2102afed-94c7-46fe-90f2-7fff290637b4" }
The sample environment response.
{ "id": "env123", "definition": { "name": "development", "description": "The environment development.", "authorizations": { "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }, "inputs": { "resource_group": "stage", "region": "us-south" }, "compliance_profile": { "id": "some-profile-id", "instance_id": "some-instance-id", "instance_location": "us-south", "profile_name": "some-profile-name", "attachment_id": "some-attachment-id" } }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "created_at": "2023-06-29T03:28:14.709Z", "modified_at": "2023-06-29T03:28:14.709Z", "href": "https://projects.api.test.cloud.ibm.com/v1/projects/6fd53106-7ce6-429e-8c57-f22e832d0c4b/environments/2102afed-94c7-46fe-90f2-7fff290637b4" }
List environments
List all available environments. For more information, see Creating an environment.
List all available environments. For more information, see Creating an environment.
List all available environments. For more information, see Creating an environment.
List all available environments. For more information, see Creating an environment.
GET /v1/projects/{project_id}/environments
list_project_environments(
self,
project_id: str,
*,
token: Optional[str] = None,
limit: Optional[int] = None,
**kwargs,
) -> DetailedResponse
listProjectEnvironments(params)
(project *ProjectV1) ListProjectEnvironments(listProjectEnvironmentsOptions *ListProjectEnvironmentsOptions) (result *EnvironmentCollection, response *core.DetailedResponse, err error)
(project *ProjectV1) ListProjectEnvironmentsWithContext(ctx context.Context, listProjectEnvironmentsOptions *ListProjectEnvironmentsOptions) (result *EnvironmentCollection, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the ListProjectEnvironmentsOptions
struct and set the fields to provide parameter values for the ListProjectEnvironments
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Query Parameters
The server uses this parameter to determine the first entry that is returned on the next page. If this parameter is not specified, the logical first page is returned.
Possible values: 0 ≤ length ≤ 1536, Value must match regular expression
^$|^(?!\s)(?!.*\s$)[^\x00-\x1F]*$
Default:
The maximum number of resources to return. The number of resources that are returned is the same, except for the last page.
Possible values: 1 ≤ value ≤ 100
Default:
10
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The server uses this parameter to determine the first entry that is returned on the next page. If this parameter is not specified, the logical first page is returned.
Possible values: 0 ≤ length ≤ 1536, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
The maximum number of resources to return. The number of resources that are returned is the same, except for the last page.
Possible values: 1 ≤ value ≤ 100
Default:
10
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The server uses this parameter to determine the first entry that is returned on the next page. If this parameter is not specified, the logical first page is returned.
Possible values: 0 ≤ length ≤ 1536, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
The maximum number of resources to return. The number of resources that are returned is the same, except for the last page.
Possible values: 1 ≤ value ≤ 100
Default:
10
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The ListProjectEnvironments options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The server uses this parameter to determine the first entry that is returned on the next page. If this parameter is not specified, the logical first page is returned.
Possible values: 0 ≤ length ≤ 1536, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
The maximum number of resources to return. The number of resources that are returned is the same, except for the last page.
Possible values: 1 ≤ value ≤ 100
Default:
10
Examples:10
curl -X GET --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" "{base_url}/v1/projects/{project_id}/environments"
listProjectEnvironmentsOptions := &projectv1.ListProjectEnvironmentsOptions{ ProjectID: &projectIdLink, Limit: core.Int64Ptr(int64(10)), } pager, err := projectService.NewProjectEnvironmentsPager(listProjectEnvironmentsOptions) if err != nil { panic(err) } var allResults []projectv1.Environment for pager.HasNext() { nextPage, err := pager.GetNext() if err != nil { panic(err) } allResults = append(allResults, nextPage...) } b, _ := json.MarshalIndent(allResults, "", " ") fmt.Println(string(b))
const params = { projectId: projectIdLink, limit: 10, }; const allResults = []; try { const pager = new ProjectV1.ProjectEnvironmentsPager(projectService, params); while (pager.hasNext()) { const nextPage = await pager.getNext(); expect(nextPage).not.toBeNull(); allResults.push(...nextPage); } console.log(JSON.stringify(allResults, null, 2)); } catch (err) { console.warn(err); }
all_results = [] pager = ProjectEnvironmentsPager( client=project_service, project_id=project_id_link, limit=10, ) while pager.has_next(): next_page = pager.get_next() assert next_page is not None all_results.extend(next_page) print(json.dumps(all_results, indent=2))
Response
The list environment response.
A pagination limit.
Possible values: 1 ≤ value ≤ 100
A pagination link.
A pagination link.
The environment.
Possible values: 0 ≤ number of items ≤ 100
The list environment response.
A pagination limit.
Possible values: 1 ≤ value ≤ 100
A pagination link.
- first
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A pagination link.
- next
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment.
Possible values: 0 ≤ number of items ≤ 100
- environments
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The target account ID derived from the authentication block values. The target account exists only if the environment currently has an authorization block.
Possible values: length ≤ 64, Value must match regular expression
/^[a-zA-Z0-9.-]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment definition.
- definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The list environment response.
A pagination limit.
Possible values: 1 ≤ value ≤ 100
A pagination link.
- first
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A pagination link.
- next
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment.
Possible values: 0 ≤ number of items ≤ 100
- environments
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The target account ID derived from the authentication block values. The target account exists only if the environment currently has an authorization block.
Possible values: length ≤ 64, Value must match regular expression
/^[a-zA-Z0-9.-]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment definition.
- definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The list environment response.
A pagination limit.
Possible values: 1 ≤ value ≤ 100
A pagination link.
- First
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A pagination link.
- Next
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment.
Possible values: 0 ≤ number of items ≤ 100
- Environments
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The project that is referenced by this resource.
- Project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- Definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The target account ID derived from the authentication block values. The target account exists only if the environment currently has an authorization block.
Possible values: length ≤ 64, Value must match regular expression
/^[a-zA-Z0-9.-]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment definition.
- Definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- Authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- ComplianceProfile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
Status Code
The request was successful.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The sample environment response for a list.
{ "limit": 1, "first": { "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/environments?limit=1" }, "next": { "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/environments?limit=1&token=da969bff-vf9q-3t1t-b677-d6rt5c0de54e" }, "environments": [ { "id": "env123", "definition": { "name": "development", "description": "The environment development.", "authorizations": { "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }, "inputs": { "resource_group": "stage", "region": "us-south" }, "compliance_profile": { "id": "some-profile-id", "instance_id": "some-instance-id", "instance_location": "us-south", "profile_name": "some-profile-name", "attachment_id": "some-attachment-id" } }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "created_at": "2023-06-29T03:28:14.709Z", "modified_at": "2023-06-29T03:28:14.709Z", "href": "https://projects.api.test.cloud.ibm.com/v1/projects/6fd53106-7ce6-429e-8c57-f22e832d0c4b/environments/2102afed-94c7-46fe-90f2-7fff290637b4" } ] }
The sample environment response for a list.
{ "limit": 1, "first": { "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/environments?limit=1" }, "next": { "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/environments?limit=1&token=da969bff-vf9q-3t1t-b677-d6rt5c0de54e" }, "environments": [ { "id": "env123", "definition": { "name": "development", "description": "The environment development.", "authorizations": { "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }, "inputs": { "resource_group": "stage", "region": "us-south" }, "compliance_profile": { "id": "some-profile-id", "instance_id": "some-instance-id", "instance_location": "us-south", "profile_name": "some-profile-name", "attachment_id": "some-attachment-id" } }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "created_at": "2023-06-29T03:28:14.709Z", "modified_at": "2023-06-29T03:28:14.709Z", "href": "https://projects.api.test.cloud.ibm.com/v1/projects/6fd53106-7ce6-429e-8c57-f22e832d0c4b/environments/2102afed-94c7-46fe-90f2-7fff290637b4" } ] }
Get an environment
Get an environment. Learn more.
Get an environment. Learn more.
Get an environment. Learn more.
Get an environment. Learn more.
GET /v1/projects/{project_id}/environments/{id}
get_project_environment(
self,
project_id: str,
id: str,
**kwargs,
) -> DetailedResponse
getProjectEnvironment(params)
(project *ProjectV1) GetProjectEnvironment(getProjectEnvironmentOptions *GetProjectEnvironmentOptions) (result *Environment, response *core.DetailedResponse, err error)
(project *ProjectV1) GetProjectEnvironmentWithContext(ctx context.Context, getProjectEnvironmentOptions *GetProjectEnvironmentOptions) (result *Environment, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the GetProjectEnvironmentOptions
struct and set the fields to provide parameter values for the GetProjectEnvironment
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The environment ID.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(?!\s)(?!.*\s$).+$
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The environment ID.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The environment ID.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The GetProjectEnvironment options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The environment ID.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
curl -X GET --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" "{base_url}/v1/projects/{project_id}/environments/{id}"
getProjectEnvironmentOptions := projectService.NewGetProjectEnvironmentOptions( projectIdLink, projectIdLink, ) environment, response, err := projectService.GetProjectEnvironment(getProjectEnvironmentOptions) if err != nil { panic(err) } b, _ := json.MarshalIndent(environment, "", " ") fmt.Println(string(b))
const params = { projectId: projectIdLink, id: projectIdLink, }; let res; try { res = await projectService.getProjectEnvironment(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
response = project_service.get_project_environment( project_id=project_id_link, id=project_id_link, ) environment = response.get_result() print(json.dumps(environment, indent=2))
Response
The definition of a project environment.
The environment definition.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(http(s)?:\/\/)[a-zA-Z0-9\$\-_\.+!\*'\(\),=&?\/]+$
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(?!\s)(?!.*\s$).+$
The project that is referenced by this resource.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The target account ID derived from the authentication block values. The target account exists only if the environment currently has an authorization block.
Possible values: length ≤ 64, Value must match regular expression
^[a-zA-Z0-9.-]+$
The definition of a project environment.
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The target account ID derived from the authentication block values. The target account exists only if the environment currently has an authorization block.
Possible values: length ≤ 64, Value must match regular expression
/^[a-zA-Z0-9.-]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment definition.
- definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The definition of a project environment.
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The target account ID derived from the authentication block values. The target account exists only if the environment currently has an authorization block.
Possible values: length ≤ 64, Value must match regular expression
/^[a-zA-Z0-9.-]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment definition.
- definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The definition of a project environment.
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The project that is referenced by this resource.
- Project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- Definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The target account ID derived from the authentication block values. The target account exists only if the environment currently has an authorization block.
Possible values: length ≤ 64, Value must match regular expression
/^[a-zA-Z0-9.-]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment definition.
- Definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- Authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- ComplianceProfile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
Status Code
You successfully retrieved an environment.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The sample environment response.
{ "id": "env123", "definition": { "name": "development", "description": "The environment development.", "authorizations": { "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }, "inputs": { "resource_group": "stage", "region": "us-south" }, "compliance_profile": { "id": "some-profile-id", "instance_id": "some-instance-id", "instance_location": "us-south", "profile_name": "some-profile-name", "attachment_id": "some-attachment-id" } }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "created_at": "2023-06-29T03:28:14.709Z", "modified_at": "2023-06-29T03:28:14.709Z", "href": "https://projects.api.test.cloud.ibm.com/v1/projects/6fd53106-7ce6-429e-8c57-f22e832d0c4b/environments/2102afed-94c7-46fe-90f2-7fff290637b4" }
The sample environment response.
{ "id": "env123", "definition": { "name": "development", "description": "The environment development.", "authorizations": { "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }, "inputs": { "resource_group": "stage", "region": "us-south" }, "compliance_profile": { "id": "some-profile-id", "instance_id": "some-instance-id", "instance_location": "us-south", "profile_name": "some-profile-name", "attachment_id": "some-attachment-id" } }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "created_at": "2023-06-29T03:28:14.709Z", "modified_at": "2023-06-29T03:28:14.709Z", "href": "https://projects.api.test.cloud.ibm.com/v1/projects/6fd53106-7ce6-429e-8c57-f22e832d0c4b/environments/2102afed-94c7-46fe-90f2-7fff290637b4" }
Update an environment
Update an environment by specifying its ID. Learn more.
Update an environment by specifying its ID. Learn more.
Update an environment by specifying its ID. Learn more.
Update an environment by specifying its ID. Learn more.
PATCH /v1/projects/{project_id}/environments/{id}
update_project_environment(
self,
project_id: str,
id: str,
definition: 'EnvironmentDefinitionPropertiesPatch',
**kwargs,
) -> DetailedResponse
updateProjectEnvironment(params)
(project *ProjectV1) UpdateProjectEnvironment(updateProjectEnvironmentOptions *UpdateProjectEnvironmentOptions) (result *Environment, response *core.DetailedResponse, err error)
(project *ProjectV1) UpdateProjectEnvironmentWithContext(ctx context.Context, updateProjectEnvironmentOptions *UpdateProjectEnvironmentOptions) (result *Environment, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the UpdateProjectEnvironmentOptions
struct and set the fields to provide parameter values for the UpdateProjectEnvironment
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The environment ID.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(?!\s)(?!.*\s$).+$
The request body for the updated environment document.
A sample environment update request.
{
"definition": {
"name": "development",
"description": "The environment development.",
"authorizations": {
"method": "trusted_profile",
"trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12"
},
"inputs": {
"resource_group": "stage",
"region": "us-south"
},
"compliance_profile": {
"id": "some-profile-id",
"instance_id": "some-instance-id",
"instance_location": "us-south",
"profile_name": "some-profile-name",
"attachment_id": "some-attachment-id"
}
}
}
The environment definition that is used for updates.
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The environment ID.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The environment definition that is used for updates.
- definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Allowable values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Allowable values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The environment ID.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The environment definition that is used for updates.
- definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Allowable values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Allowable values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The UpdateProjectEnvironment options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The environment ID.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The environment definition that is used for updates.
Examples:{ "name": "development", "description": "The environment development.", "authorizations": { "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }, "inputs": { "resource_group": "stage", "region": "us-south" }, "compliance_profile": { "id": "some-profile-id", "instance_id": "some-instance-id", "instance_location": "us-south", "profile_name": "some-profile-name", "attachment_id": "some-attachment-id" } }
- Definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- Authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Allowable values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- ComplianceProfile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Allowable values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
curl -X PATCH --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" --header "Content-Type: application/json" --data '{ "definition": { "name": "development", "description": "The environment development.", "authorizations": { "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }, "inputs": { "resource_group": "stage", "region": "us-south" }, "compliance_profile": { "id": "some-profile-id", "instance_id": "some-instance-id", "instance_location": "us-south", "profile_name": "some-profile-name", "attachment_id": "some-attachment-id" } } }' "{base_url}/v1/projects/{project_id}/environments/{id}"
projectConfigAuthModel := &projectv1.ProjectConfigAuth{ TrustedProfileID: core.StringPtr("Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12"), Method: core.StringPtr("trusted_profile"), } projectComplianceProfileModel := &projectv1.ProjectComplianceProfile{ ID: core.StringPtr("some-profile-id"), InstanceID: core.StringPtr("some-instance-id"), InstanceLocation: core.StringPtr("us-south"), AttachmentID: core.StringPtr("some-attachment-id"), ProfileName: core.StringPtr("some-profile-name"), } environmentDefinitionPropertiesPatchModel := &projectv1.EnvironmentDefinitionPropertiesPatch{ Description: core.StringPtr("The environment development."), Name: core.StringPtr("development"), Authorizations: projectConfigAuthModel, ComplianceProfile: projectComplianceProfileModel, } updateProjectEnvironmentOptions := projectService.NewUpdateProjectEnvironmentOptions( projectIdLink, projectIdLink, environmentDefinitionPropertiesPatchModel, ) environment, response, err := projectService.UpdateProjectEnvironment(updateProjectEnvironmentOptions) if err != nil { panic(err) } b, _ := json.MarshalIndent(environment, "", " ") fmt.Println(string(b))
// Request models needed by this operation. // ProjectConfigAuth const projectConfigAuthModel = { trusted_profile_id: 'Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12', method: 'trusted_profile', }; // ProjectComplianceProfile const projectComplianceProfileModel = { id: 'some-profile-id', instance_id: 'some-instance-id', instance_location: 'us-south', attachment_id: 'some-attachment-id', profile_name: 'some-profile-name', }; // EnvironmentDefinitionPropertiesPatch const environmentDefinitionPropertiesPatchModel = { description: 'The environment development.', name: 'development', authorizations: projectConfigAuthModel, inputs: { resource_group: 'stage', region: 'us-south' }, compliance_profile: projectComplianceProfileModel, }; const params = { projectId: projectIdLink, id: projectIdLink, definition: environmentDefinitionPropertiesPatchModel, }; let res; try { res = await projectService.updateProjectEnvironment(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
project_config_auth_model = { 'trusted_profile_id': 'Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12', 'method': 'trusted_profile', } project_compliance_profile_model = { 'id': 'some-profile-id', 'instance_id': 'some-instance-id', 'instance_location': 'us-south', 'attachment_id': 'some-attachment-id', 'profile_name': 'some-profile-name', } environment_definition_properties_patch_model = { 'description': 'The environment development.', 'name': 'development', 'authorizations': project_config_auth_model, 'inputs': {'resource_group': 'stage', 'region': 'us-south'}, 'compliance_profile': project_compliance_profile_model, } response = project_service.update_project_environment( project_id=project_id_link, id=project_id_link, definition=environment_definition_properties_patch_model, ) environment = response.get_result() print(json.dumps(environment, indent=2))
Response
The definition of a project environment.
The environment definition.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(http(s)?:\/\/)[a-zA-Z0-9\$\-_\.+!\*'\(\),=&?\/]+$
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(?!\s)(?!.*\s$).+$
The project that is referenced by this resource.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The target account ID derived from the authentication block values. The target account exists only if the environment currently has an authorization block.
Possible values: length ≤ 64, Value must match regular expression
^[a-zA-Z0-9.-]+$
The definition of a project environment.
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The target account ID derived from the authentication block values. The target account exists only if the environment currently has an authorization block.
Possible values: length ≤ 64, Value must match regular expression
/^[a-zA-Z0-9.-]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment definition.
- definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The definition of a project environment.
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The target account ID derived from the authentication block values. The target account exists only if the environment currently has an authorization block.
Possible values: length ≤ 64, Value must match regular expression
/^[a-zA-Z0-9.-]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment definition.
- definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The definition of a project environment.
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The project that is referenced by this resource.
- Project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- Definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The target account ID derived from the authentication block values. The target account exists only if the environment currently has an authorization block.
Possible values: length ≤ 64, Value must match regular expression
/^[a-zA-Z0-9.-]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The environment definition.
- Definition
The description of the environment.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The name of the environment. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- Authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- ComplianceProfile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
Status Code
You successfully updated an environment.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The sample environment response.
{ "id": "env123", "definition": { "name": "development", "description": "The environment development.", "authorizations": { "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }, "inputs": { "resource_group": "stage", "region": "us-south" }, "compliance_profile": { "id": "some-profile-id", "instance_id": "some-instance-id", "instance_location": "us-south", "profile_name": "some-profile-name", "attachment_id": "some-attachment-id" } }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "created_at": "2023-06-29T03:28:14.709Z", "modified_at": "2023-06-29T03:28:14.709Z", "href": "https://projects.api.test.cloud.ibm.com/v1/projects/6fd53106-7ce6-429e-8c57-f22e832d0c4b/environments/2102afed-94c7-46fe-90f2-7fff290637b4" }
The sample environment response.
{ "id": "env123", "definition": { "name": "development", "description": "The environment development.", "authorizations": { "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }, "inputs": { "resource_group": "stage", "region": "us-south" }, "compliance_profile": { "id": "some-profile-id", "instance_id": "some-instance-id", "instance_location": "us-south", "profile_name": "some-profile-name", "attachment_id": "some-attachment-id" } }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "created_at": "2023-06-29T03:28:14.709Z", "modified_at": "2023-06-29T03:28:14.709Z", "href": "https://projects.api.test.cloud.ibm.com/v1/projects/6fd53106-7ce6-429e-8c57-f22e832d0c4b/environments/2102afed-94c7-46fe-90f2-7fff290637b4" }
Delete an environment
Delete an environment in a project by specifying its ID.
Delete an environment in a project by specifying its ID.
Delete an environment in a project by specifying its ID.
Delete an environment in a project by specifying its ID.
DELETE /v1/projects/{project_id}/environments/{id}
delete_project_environment(
self,
project_id: str,
id: str,
**kwargs,
) -> DetailedResponse
deleteProjectEnvironment(params)
(project *ProjectV1) DeleteProjectEnvironment(deleteProjectEnvironmentOptions *DeleteProjectEnvironmentOptions) (result *EnvironmentDeleteResponse, response *core.DetailedResponse, err error)
(project *ProjectV1) DeleteProjectEnvironmentWithContext(ctx context.Context, deleteProjectEnvironmentOptions *DeleteProjectEnvironmentOptions) (result *EnvironmentDeleteResponse, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the DeleteProjectEnvironmentOptions
struct and set the fields to provide parameter values for the DeleteProjectEnvironment
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The environment ID.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(?!\s)(?!.*\s$).+$
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The environment ID.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The environment ID.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The DeleteProjectEnvironment options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The environment ID.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
curl -X DELETE --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" "{base_url}/v1/projects/{project_id}/environments/{id}"
deleteProjectEnvironmentOptions := projectService.NewDeleteProjectEnvironmentOptions( projectIdLink, projectIdLink, ) environmentDeleteResponse, response, err := projectService.DeleteProjectEnvironment(deleteProjectEnvironmentOptions) if err != nil { panic(err) } b, _ := json.MarshalIndent(environmentDeleteResponse, "", " ") fmt.Println(string(b))
const params = { projectId: projectIdLink, id: projectIdLink, }; let res; try { res = await projectService.deleteProjectEnvironment(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
response = project_service.delete_project_environment( project_id=project_id_link, id=project_id_link, ) environment_delete_response = response.get_result() print(json.dumps(environment_delete_response, indent=2))
Response
The response to a request to delete an environment.
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(?!\s)(?!.*\s$).+$
The response to a request to delete an environment.
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The response to a request to delete an environment.
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The response to a request to delete an environment.
The environment ID as a friendly name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
Status Code
You successfully deleted an environment.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The sample environment delete response.
{ "id": "env123" }
The sample environment delete response.
{ "id": "env123" }
Add or remove resources
Add or remove existing resources from a configuration by adding or removing service tags. Service tags are static and already part of the model. The request does not require a payload.
POST /v1/projects/{project_id}/configs/{id}/apply_tags
Authentication
Add a new configuration
Add a new configuration to a project.
Add a new configuration to a project.
Add a new configuration to a project.
Add a new configuration to a project.
POST /v1/projects/{project_id}/configs
create_config(
self,
project_id: str,
definition: 'ProjectConfigDefinitionPrototype',
*,
schematics: Optional['SchematicsWorkspace'] = None,
**kwargs,
) -> DetailedResponse
createConfig(params)
(project *ProjectV1) CreateConfig(createConfigOptions *CreateConfigOptions) (result *ProjectConfig, response *core.DetailedResponse, err error)
(project *ProjectV1) CreateConfigWithContext(ctx context.Context, createConfigOptions *CreateConfigOptions) (result *ProjectConfig, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the CreateConfigOptions
struct and set the fields to provide parameter values for the CreateConfig
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The request body for the new project definition document.
An example request for a project configuration with a catalog locator ID.
{
"definition": {
"name": "env-stage",
"description": "The stage environment configuration.",
"locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global",
"inputs": {
"account_id": "account_id",
"resource_group": "stage",
"access_tags": [
"env:stage"
],
"logdna_name": "LogDNA_stage_service",
"sysdig_name": "SysDig_stage_service"
}
}
}
A resource configuration example request.
{
"definition": {
"name": "shared-resources-dev",
"description": "The stage environment configuration.",
"labels": [
"dev"
],
"resource_crns": [
"crn:v1:staging:public:continuous-delivery:us-south:a/d11256044e024d5bbea1a7d7ee4575c3:e988fcf7-2bd7-46de-a72d-339ebe859a9e::",
"crn:v1:staging:public:toolchain:us-south:a/d11256044e024d5bbea1a7d7ee4575c3:618c70c7-0ead-40fb-86ce-e3f7b10c9f99::"
],
"authorizations": {
"method": "trusted_profile",
"trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12"
}
}
}
A project configuration example request for importing from an existing workspace.
{
"definition": {
"name": "env-stage",
"description": "The stage environment configuration.",
"inputs": {
"account_id": "account_id",
"resource_group": "stage",
"access_tags": [
"env:stage"
],
"logdna_name": "LogDNA_stage_service",
"sysdig_name": "SysDig_stage_service"
}
},
"schematics": {
"workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139"
}
}
The example request to create a stack configuration.
{
"definition": {
"name": "stack-bottom-up-example",
"description": "A deployable architecture stack that includes two member deployable architectures.",
"members": [
{
"name": "foundation-deployable-architecture",
"config_id": "293c3c36-a094-4115-a12b-de0a9ca39beX"
},
{
"name": "middleware-architecture",
"config_id": "293c3c36-a094-4115-a12b-de0a9ca39be5"
}
]
}
}
A Schematics workspace to use for deploying this deployable architecture.
If you are importing data from an existing Schematics workspace that is not backed by cart, then you must provide a
locator_id
. If you are using a Schematics workspace that is backed by cart, alocator_id
is not required because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
code is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace.
For more information, see Creating workspaces and importing your Terraform template.
- If only a
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Allowable values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Allowable values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A Schematics workspace to use for deploying this deployable architecture.
If you are importing data from an existing Schematics workspace that is not backed by cart, then you must provide a
locator_id
. If you are using a Schematics workspace that is backed by cart, alocator_id
is not required because the Schematics workspace has one. There are 3 scenarios:- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
code is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information, see Creating workspaces and importing your Terraform template.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
- If only a
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Allowable values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Allowable values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A Schematics workspace to use for deploying this deployable architecture.
If you are importing data from an existing Schematics workspace that is not backed by cart, then you must provide a
locator_id
. If you are using a Schematics workspace that is backed by cart, alocator_id
is not required because the Schematics workspace has one. There are 3 scenarios:- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
code is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information, see Creating workspaces and importing your Terraform template.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
- If only a
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The CreateConfig options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The description of a project configuration.
- Definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- ComplianceProfile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Allowable values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- Authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Allowable values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A Schematics workspace to use for deploying this deployable architecture.
If you are importing data from an existing Schematics workspace that is not backed by cart, then you must provide a
locator_id
. If you are using a Schematics workspace that is backed by cart, alocator_id
is not required because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
code is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace.
For more information, see Creating workspaces and importing your Terraform template.
- Schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
- If only a
curl -X POST --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" --header "Content-Type: application/json" --data '{ "definition": { "name": "env-stage", "description": "The stage environment configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "account_id", "resource_group": "stage", "access_tags": [ "env:stage" ], "logdna_name": "LogDNA_stage_service", "sysdig_name": "SysDig_stage_service" } } }' "{base_url}/v1/projects/{project_id}/configs"
projectConfigDefinitionPrototypeModel := &projectv1.ProjectConfigDefinitionPrototypeDAConfigDefinitionPropertiesPrototype{ LocatorID: core.StringPtr("1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global"), Description: core.StringPtr("The stage environment configuration."), Name: core.StringPtr("env-stage"), } createConfigOptions := projectService.NewCreateConfigOptions( projectIdLink, projectConfigDefinitionPrototypeModel, ) projectConfig, response, err := projectService.CreateConfig(createConfigOptions) if err != nil { panic(err) } b, _ := json.MarshalIndent(projectConfig, "", " ") fmt.Println(string(b))
// Request models needed by this operation. // ProjectConfigDefinitionPrototypeDAConfigDefinitionPropertiesPrototype const projectConfigDefinitionPrototypeModel = { locator_id: '1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global', description: 'The stage environment configuration.', name: 'env-stage', inputs: { account_id: 'account_id', resource_group: 'stage', access_tags: ['env:stage'], logdna_name: 'LogDNA_stage_service', sysdig_name: 'SysDig_stage_service' }, }; const params = { projectId: projectIdLink, definition: projectConfigDefinitionPrototypeModel, }; let res; try { res = await projectService.createConfig(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
project_config_definition_prototype_model = { 'locator_id': '1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global', 'description': 'The stage environment configuration.', 'name': 'env-stage', 'inputs': {'account_id': 'account_id', 'resource_group': 'stage', 'access_tags': ['env:stage'], 'logdna_name': 'LogDNA_stage_service', 'sysdig_name': 'SysDig_stage_service'}, } response = project_service.create_config( project_id=project_id_link, definition=project_config_definition_prototype_model, ) project_config = response.get_result() print(json.dumps(project_config, indent=2))
Response
The standard schema of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
The project that is referenced by this resource.
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(http(s)?:\/\/)[a-zA-Z0-9\$\-_\.+!\*'\(\),=&?\/]+$
The last approved metadata of the configuration.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The href and results from the last action job that is performed on the project configuration.
The href and results from the last action job that is performed on the project configuration.
The href and results from the last action job that is performed on the project configuration.
The summary from the last monitoring action job that is performed on the project configuration.
The references that are used in the configuration to resolve input values.
- references
A Schematics workspace that is associated to a project configuration, with scripts.
The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The stack config parent of which this configuration is a member of.
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]A summary of a project configuration version.
A summary of a project configuration version.
The standard schema of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- needs_attention_state
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- last_approved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_validated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- cost_estimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- cra_logs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_deployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- last_undeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- last_monitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- drift_detection
A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- member_of
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A summary of a project configuration version.
- approved_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A summary of a project configuration version.
- deployed_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The standard schema of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- needs_attention_state
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- last_approved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_validated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- cost_estimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- cra_logs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_deployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- last_undeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- last_monitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- drift_detection
A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- member_of
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A summary of a project configuration version.
- approved_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A summary of a project configuration version.
- deployed_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The standard schema of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- NeedsAttentionState
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- LastApproved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- LastValidated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- CostEstimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- CraLogs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- Summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- LastDeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- LastUndeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- LastMonitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- DriftDetection
A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- Outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- Project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- Definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- Schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- ValidatePreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- ValidatePostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- DeployPreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- DeployPostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- UndeployPreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- UndeployPostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- MemberOf
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- Definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- Members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- Definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- ComplianceProfile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- Authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A summary of a project configuration version.
- ApprovedVersion
A summary of the definition in a project configuration version.
- Definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A summary of a project configuration version.
- DeployedVersion
A summary of the definition in a project configuration version.
- Definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
Status Code
The new resource was created.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The example response to a request for a deployable architecture configuration draft.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "env-stage", "description": "The stage environment configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "ref:/configs/account-stage/inputs/account_id", "resource_group": "stage", "access_tags": [ "env:stage" ], "logdna_name": "The name of the LogDNA stage service instance.", "sysdig_name": "The name of the SysDig stage service instance." } }, "is_draft": true, "version": 2, "outputs": [ { "name": "resource_group_id" }, { "name": "logdna_id" }, { "name": "sysdig_id" } ], "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "schematics": { "workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139" }, "state": "validated", "update_available": true, "needs_attention_state": [], "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/b0c44146-1ef6-40c2-82ba-74d51149770a", "deployment_mode": "project_deployed" }
The example response to a request for a deployable architecture configuration draft.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "env-stage", "description": "The stage environment configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "ref:/configs/account-stage/inputs/account_id", "resource_group": "stage", "access_tags": [ "env:stage" ], "logdna_name": "The name of the LogDNA stage service instance.", "sysdig_name": "The name of the SysDig stage service instance." } }, "is_draft": true, "version": 2, "outputs": [ { "name": "resource_group_id" }, { "name": "logdna_id" }, { "name": "sysdig_id" } ], "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "schematics": { "workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139" }, "state": "validated", "update_available": true, "needs_attention_state": [], "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/b0c44146-1ef6-40c2-82ba-74d51149770a", "deployment_mode": "project_deployed" }
The example response to a request for a resource configuration draft.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "shared-resources-dev", "description": "The shared resources for dev environments.", "labels": [ "dev" ], "type": "manual", "resource_crns": [ "crn:v1:staging:public:toolchain:us-south:a/d11256044e024d5bbea1a7d7ee4575c3:618c70c7-0ead-40fb-86ce-e3f7b10c9f99::" ] }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "is_draft": false, "version": 2, "state": "applied", "needs_attention_state": [], "outputs": [], "created_at": "2023-02-22T19:51:23.253Z", "updated_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/293c3c36-a094-4115-a12b-de0a9ca39be5", "deployment_mode": "user_deployed" }
The example response to a request for a resource configuration draft.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "shared-resources-dev", "description": "The shared resources for dev environments.", "labels": [ "dev" ], "type": "manual", "resource_crns": [ "crn:v1:staging:public:toolchain:us-south:a/d11256044e024d5bbea1a7d7ee4575c3:618c70c7-0ead-40fb-86ce-e3f7b10c9f99::" ] }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "is_draft": false, "version": 2, "state": "applied", "needs_attention_state": [], "outputs": [], "created_at": "2023-02-22T19:51:23.253Z", "updated_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/293c3c36-a094-4115-a12b-de0a9ca39be5", "deployment_mode": "user_deployed" }
Sample response to consume a stack.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "stack-config-example", "description": "A deployable architecture stack that substitutes the first member in a stack for another existing configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "region": "us-south", "resource_group_name": "stack-rg" }, "members": [ { "name": "foundation-deployable-architecture", "config_id": "293c3c36-a094-4115-a12b-de0a9ca39beX" }, { "name": "middleware-architecture", "config_id": "293c3c36-a094-4115-a12b-de0a9ca39beZ" } ] }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "version": 1, "is_draft": true, "state": "draft", "needs_attention_state": [], "outputs": [ { "name": "workload_cluster_server_url" } ], "created_at": "2023-02-22T19:51:23.253Z", "updated_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/293c3c36-a094-4115-a12b-de0a9ca39be5" }
Sample response to consume a stack.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "stack-config-example", "description": "A deployable architecture stack that substitutes the first member in a stack for another existing configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "region": "us-south", "resource_group_name": "stack-rg" }, "members": [ { "name": "foundation-deployable-architecture", "config_id": "293c3c36-a094-4115-a12b-de0a9ca39beX" }, { "name": "middleware-architecture", "config_id": "293c3c36-a094-4115-a12b-de0a9ca39beZ" } ] }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "version": 1, "is_draft": true, "state": "draft", "needs_attention_state": [], "outputs": [ { "name": "workload_cluster_server_url" } ], "created_at": "2023-02-22T19:51:23.253Z", "updated_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/293c3c36-a094-4115-a12b-de0a9ca39be5" }
Sample response to create a stack.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "stack-bottom-up-example", "description": "A deployable architecture stack that includes two member deployable architectures.", "members": [ { "name": "foundation-deployable-architecture", "config_id": "293c3c36-a094-4115-a12b-de0a9ca39beX" }, { "name": "middleware-architecture", "config_id": "293c3c36-a094-4115-a12b-de0a9ca39be5" } ] }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "version": 1, "is_draft": true, "state": "draft", "needs_attention_state": [], "outputs": [], "created_at": "2023-02-22T19:51:23.253Z", "updated_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/293c3c36-a094-4115-a12b-de0a9ca39be5" }
Sample response to create a stack.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "stack-bottom-up-example", "description": "A deployable architecture stack that includes two member deployable architectures.", "members": [ { "name": "foundation-deployable-architecture", "config_id": "293c3c36-a094-4115-a12b-de0a9ca39beX" }, { "name": "middleware-architecture", "config_id": "293c3c36-a094-4115-a12b-de0a9ca39be5" } ] }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "version": 1, "is_draft": true, "state": "draft", "needs_attention_state": [], "outputs": [], "created_at": "2023-02-22T19:51:23.253Z", "updated_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/293c3c36-a094-4115-a12b-de0a9ca39be5" }
List all project configurations
Retrieve the collection of configurations.
Retrieve the collection of configurations.
Retrieve the collection of configurations.
Retrieve the collection of configurations.
GET /v1/projects/{project_id}/configs
list_configs(
self,
project_id: str,
*,
token: Optional[str] = None,
limit: Optional[int] = None,
**kwargs,
) -> DetailedResponse
listConfigs(params)
(project *ProjectV1) ListConfigs(listConfigsOptions *ListConfigsOptions) (result *ProjectConfigCollection, response *core.DetailedResponse, err error)
(project *ProjectV1) ListConfigsWithContext(ctx context.Context, listConfigsOptions *ListConfigsOptions) (result *ProjectConfigCollection, response *core.DetailedResponse, err error)
Request
Instantiate the ListConfigsOptions
struct and set the fields to provide parameter values for the ListConfigs
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Query Parameters
The server uses this parameter to determine the first entry that is returned on the next page. If this parameter is not specified, the logical first page is returned.
Possible values: 0 ≤ length ≤ 1536, Value must match regular expression
^$|^(?!\s)(?!.*\s$)[^\x00-\x1F]*$
Default:
The maximum number of resources to return. The number of resources that are returned is the same, except for the last page.
Possible values: 1 ≤ value ≤ 100
Default:
10
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The server uses this parameter to determine the first entry that is returned on the next page. If this parameter is not specified, the logical first page is returned.
Possible values: 0 ≤ length ≤ 1536, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
The maximum number of resources to return. The number of resources that are returned is the same, except for the last page.
Possible values: 1 ≤ value ≤ 100
Default:
10
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The server uses this parameter to determine the first entry that is returned on the next page. If this parameter is not specified, the logical first page is returned.
Possible values: 0 ≤ length ≤ 1536, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
The maximum number of resources to return. The number of resources that are returned is the same, except for the last page.
Possible values: 1 ≤ value ≤ 100
Default:
10
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The ListConfigs options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The server uses this parameter to determine the first entry that is returned on the next page. If this parameter is not specified, the logical first page is returned.
Possible values: 0 ≤ length ≤ 1536, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
Default:
The maximum number of resources to return. The number of resources that are returned is the same, except for the last page.
Possible values: 1 ≤ value ≤ 100
Default:
10
Examples:10
curl -X GET --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" "{base_url}/v1/projects/{project_id}/configs"
listConfigsOptions := &projectv1.ListConfigsOptions{ ProjectID: &projectIdLink, Limit: core.Int64Ptr(int64(10)), } pager, err := projectService.NewConfigsPager(listConfigsOptions) if err != nil { panic(err) } var allResults []projectv1.ProjectConfigSummary for pager.HasNext() { nextPage, err := pager.GetNext() if err != nil { panic(err) } allResults = append(allResults, nextPage...) } b, _ := json.MarshalIndent(allResults, "", " ") fmt.Println(string(b))
const params = { projectId: projectIdLink, limit: 10, }; const allResults = []; try { const pager = new ProjectV1.ConfigsPager(projectService, params); while (pager.hasNext()) { const nextPage = await pager.getNext(); expect(nextPage).not.toBeNull(); allResults.push(...nextPage); } console.log(JSON.stringify(allResults, null, 2)); } catch (err) { console.warn(err); }
all_results = [] pager = ConfigsPager( client=project_service, project_id=project_id_link, limit=10, ) while pager.has_next(): next_page = pager.get_next() assert next_page is not None all_results.extend(next_page) print(json.dumps(all_results, indent=2))
Response
The project configuration list.
A pagination limit.
Possible values: 1 ≤ value ≤ 100
A pagination link.
A pagination link.
The response schema of the collection list operation that defines the array property with the name
configs
.Possible values: 0 ≤ number of items ≤ 20
The project configuration list.
A pagination limit.
Possible values: 1 ≤ value ≤ 100
A pagination link.
- first
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A pagination link.
- next
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The response schema of the collection list operation that defines the array property with the name
configs
.Possible values: 0 ≤ number of items ≤ 20
- configs
A summary of a project configuration version.
- approved_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A summary of a project configuration version.
- deployed_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The description of a project configuration.
- definition
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]
The project configuration list.
A pagination limit.
Possible values: 1 ≤ value ≤ 100
A pagination link.
- first
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A pagination link.
- next
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The response schema of the collection list operation that defines the array property with the name
configs
.Possible values: 0 ≤ number of items ≤ 20
- configs
A summary of a project configuration version.
- approved_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A summary of a project configuration version.
- deployed_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The description of a project configuration.
- definition
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]
The project configuration list.
A pagination limit.
Possible values: 1 ≤ value ≤ 100
A pagination link.
- First
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A pagination link.
- Next
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The response schema of the collection list operation that defines the array property with the name
configs
.Possible values: 0 ≤ number of items ≤ 20
- Configs
A summary of a project configuration version.
- ApprovedVersion
A summary of the definition in a project configuration version.
- Definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A summary of a project configuration version.
- DeployedVersion
A summary of the definition in a project configuration version.
- Definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The description of a project configuration.
- Definition
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The project that is referenced by this resource.
- Project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- Definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]
Status Code
The request was successful.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The example response for a request to get project configurations.
{ "limit": 2, "first": { "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs?limit=2" }, "next": { "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs?limit=2&token=da969bff-vf9q-3t1t-b677-d6rt5c0de54e" }, "configs": [ { "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "env-stage", "description": "The stage environment configuration." }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "version": 1, "state": "validated", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/db268db0-160b-4911-8f93-89659000a927/configs/293c3c36-a094-4115-a12b-de0a9ca39be5" }, { "id": "9c7afed6-17fb-4c56-a13d-440a78f936bd", "definition": { "name": "region-eu-de-stage", "description": "The stage `eu-de` configuration." }, "approved_version": { "definition": { "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global" }, "version": 1, "state": "approved", "href": "https://projects.api.cloud.ibm.com/v1/projects/db268db0-160b-4911-8f93-89659000a927/configs/9c7afed6-17fb-4c56-a13d-440a78f936bd/versions/1" }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "version": 2, "state": "draft", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/db268db0-160b-4911-8f93-89659000a927/configs/9c7afed6-17fb-4c56-a13d-440a78f936bd" } ] }
The example response for a request to get project configurations.
{ "limit": 2, "first": { "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs?limit=2" }, "next": { "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs?limit=2&token=da969bff-vf9q-3t1t-b677-d6rt5c0de54e" }, "configs": [ { "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "env-stage", "description": "The stage environment configuration." }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "version": 1, "state": "validated", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/db268db0-160b-4911-8f93-89659000a927/configs/293c3c36-a094-4115-a12b-de0a9ca39be5" }, { "id": "9c7afed6-17fb-4c56-a13d-440a78f936bd", "definition": { "name": "region-eu-de-stage", "description": "The stage `eu-de` configuration." }, "approved_version": { "definition": { "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global" }, "version": 1, "state": "approved", "href": "https://projects.api.cloud.ibm.com/v1/projects/db268db0-160b-4911-8f93-89659000a927/configs/9c7afed6-17fb-4c56-a13d-440a78f936bd/versions/1" }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "version": 2, "state": "draft", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/db268db0-160b-4911-8f93-89659000a927/configs/9c7afed6-17fb-4c56-a13d-440a78f936bd" } ] }
Get a project configuration
Retrieve the specified project configuration in a specific project. For more information about project configurations, see Monitoring the status of a configuration and its resources.
Retrieve the specified project configuration in a specific project. For more information about project configurations, see Monitoring the status of a configuration and its resources.
Retrieve the specified project configuration in a specific project. For more information about project configurations, see Monitoring the status of a configuration and its resources.
Retrieve the specified project configuration in a specific project. For more information about project configurations, see Monitoring the status of a configuration and its resources.
GET /v1/projects/{project_id}/configs/{id}
get_config(
self,
project_id: str,
id: str,
**kwargs,
) -> DetailedResponse
getConfig(params)
(project *ProjectV1) GetConfig(getConfigOptions *GetConfigOptions) (result *ProjectConfig, response *core.DetailedResponse, err error)
(project *ProjectV1) GetConfigWithContext(ctx context.Context, getConfigOptions *GetConfigOptions) (result *ProjectConfig, response *core.DetailedResponse, err error)
Request
Instantiate the GetConfigOptions
struct and set the fields to provide parameter values for the GetConfig
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The GetConfig options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
curl -X GET --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" "{base_url}/v1/projects/{project_id}/configs/{id}"
getConfigOptions := projectService.NewGetConfigOptions( projectIdLink, configIdLink, ) projectConfig, response, err := projectService.GetConfig(getConfigOptions) if err != nil { panic(err) } b, _ := json.MarshalIndent(projectConfig, "", " ") fmt.Println(string(b))
const params = { projectId: projectIdLink, id: configIdLink, }; let res; try { res = await projectService.getConfig(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
response = project_service.get_config( project_id=project_id_link, id=config_id_link, ) project_config = response.get_result() print(json.dumps(project_config, indent=2))
Response
The standard schema of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
The project that is referenced by this resource.
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(http(s)?:\/\/)[a-zA-Z0-9\$\-_\.+!\*'\(\),=&?\/]+$
The last approved metadata of the configuration.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The href and results from the last action job that is performed on the project configuration.
The href and results from the last action job that is performed on the project configuration.
The href and results from the last action job that is performed on the project configuration.
The summary from the last monitoring action job that is performed on the project configuration.
The references that are used in the configuration to resolve input values.
- references
A Schematics workspace that is associated to a project configuration, with scripts.
The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The stack config parent of which this configuration is a member of.
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]A summary of a project configuration version.
A summary of a project configuration version.
The standard schema of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- needs_attention_state
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- last_approved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_validated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- cost_estimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- cra_logs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_deployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- last_undeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- last_monitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- drift_detection
A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- member_of
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A summary of a project configuration version.
- approved_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A summary of a project configuration version.
- deployed_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The standard schema of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- needs_attention_state
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- last_approved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_validated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- cost_estimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- cra_logs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_deployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- last_undeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- last_monitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- drift_detection
A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- member_of
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A summary of a project configuration version.
- approved_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A summary of a project configuration version.
- deployed_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The standard schema of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- NeedsAttentionState
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- LastApproved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- LastValidated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- CostEstimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- CraLogs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- Summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- LastDeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- LastUndeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- LastMonitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- DriftDetection
A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- Outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- Project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- Definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- Schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- ValidatePreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- ValidatePostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- DeployPreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- DeployPostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- UndeployPreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- UndeployPostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- MemberOf
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- Definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- Members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- Definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- ComplianceProfile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- Authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A summary of a project configuration version.
- ApprovedVersion
A summary of the definition in a project configuration version.
- Definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A summary of a project configuration version.
- DeployedVersion
A summary of the definition in a project configuration version.
- Definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
Status Code
The request was successful.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The example response for a deployable architecture configuration.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "env-stage", "description": "The stage environment configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "ref:/configs/account-stage/inputs/account_id", "resource_group": "stage", "access_tags": [ "env:stage" ], "logdna_name": "The name of the LogDNA stage service instance.", "sysdig_name": "The name of the SysDig stage service instance." } }, "needs_attention_state": [], "approved_version": { "definition": { "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global" }, "version": 1, "state": "approved", "href": "https://projects.api.cloud.ibm.com/v1/projects/db268db0-160b-4911-8f93-89659000a927/configs/9c7afed6-17fb-4c56-a13d-440a78f936bd/versions/1" }, "deployed_version": { "definition": { "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global" }, "version": 1, "state": "deployed", "href": "https://projects.api.cloud.ibm.com/v1/projects/db268db0-160b-4911-8f93-89659000a927/configs/9c7afed6-17fb-4c56-a13d-440a78f936bd/versions/1" }, "last_validated": { "cost_estimate": {}, "cra_logs": {}, "job": { "id": "ba98208b61efa490153b72adfd672251", "summary": { "version": "1.0.5", "plan_summary": {}, "apply_summary": {}, "destroy_summary": {}, "message_summary": {}, "plan_messages": {}, "apply_messages": {}, "destroy_messages": {} } }, "href": "https://projects.api.cloud.ibm.com/v1/projects/606bdec6-3b18-4c5e-9cf5-64ff228ab4f6/configs/ac0f34f7-1efc-408c-8a7f-eaa2c9d2bb64/versions/1/last_validated", "result": "passed" }, "last_deployed": { "job": { "id": "c646f6bd5921e5a56656818cc4a22bea", "summary": { "version": "1.0.5", "plan_summary": {}, "apply_summary": {}, "destroy_summary": {}, "message_summary": {}, "plan_messages": {}, "apply_messages": {}, "destroy_messages": {} } }, "href": "https://projects.api.cloud.ibm.com/v1/projects/606bdec6-3b18-4c5e-9cf5-64ff228ab4f6/configs/ac0f34f7-1efc-408c-8a7f-eaa2c9d2bb64/versions/1/last_deployed", "result": "passed" }, "last_undeployed": { "job": { "id": "55ced596251e5fcfe86814d189da035e", "summary": { "version": "1.0.5", "plan_summary": {}, "apply_summary": {}, "destroy_summary": {}, "message_summary": {}, "plan_messages": {}, "apply_messages": {}, "destroy_messages": {} } }, "href": "https://projects.api.cloud.ibm.com/v1/projects/606bdec6-3b18-4c5e-9cf5-64ff228ab4f6/configs/ac0f34f7-1efc-408c-8a7f-eaa2c9d2bb64/versions/1/last_undeployed", "result": "failed" }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "version": 2, "is_draft": true, "outputs": [ { "name": "resource_group_id" }, { "name": "logdna_id" }, { "name": "sysdig_id" } ], "schematics": { "workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139", "validate_pre_script": { "type": "ansible", "path": "scripts/validate-pre-ansible-playbook.yaml", "short_description": "pre-validate" }, "validate_post_script": { "type": "ansible", "path": "scripts/validate-post-ansible-playbook.yaml", "short_description": "post validate" } }, "state": "draft", "update_available": true, "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/b0c44146-1ef6-40c2-82ba-74d51149770a", "deployment_mode": "project_deployed" }
The example response for a deployable architecture configuration.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "env-stage", "description": "The stage environment configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "ref:/configs/account-stage/inputs/account_id", "resource_group": "stage", "access_tags": [ "env:stage" ], "logdna_name": "The name of the LogDNA stage service instance.", "sysdig_name": "The name of the SysDig stage service instance." } }, "needs_attention_state": [], "approved_version": { "definition": { "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global" }, "version": 1, "state": "approved", "href": "https://projects.api.cloud.ibm.com/v1/projects/db268db0-160b-4911-8f93-89659000a927/configs/9c7afed6-17fb-4c56-a13d-440a78f936bd/versions/1" }, "deployed_version": { "definition": { "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global" }, "version": 1, "state": "deployed", "href": "https://projects.api.cloud.ibm.com/v1/projects/db268db0-160b-4911-8f93-89659000a927/configs/9c7afed6-17fb-4c56-a13d-440a78f936bd/versions/1" }, "last_validated": { "cost_estimate": {}, "cra_logs": {}, "job": { "id": "ba98208b61efa490153b72adfd672251", "summary": { "version": "1.0.5", "plan_summary": {}, "apply_summary": {}, "destroy_summary": {}, "message_summary": {}, "plan_messages": {}, "apply_messages": {}, "destroy_messages": {} } }, "href": "https://projects.api.cloud.ibm.com/v1/projects/606bdec6-3b18-4c5e-9cf5-64ff228ab4f6/configs/ac0f34f7-1efc-408c-8a7f-eaa2c9d2bb64/versions/1/last_validated", "result": "passed" }, "last_deployed": { "job": { "id": "c646f6bd5921e5a56656818cc4a22bea", "summary": { "version": "1.0.5", "plan_summary": {}, "apply_summary": {}, "destroy_summary": {}, "message_summary": {}, "plan_messages": {}, "apply_messages": {}, "destroy_messages": {} } }, "href": "https://projects.api.cloud.ibm.com/v1/projects/606bdec6-3b18-4c5e-9cf5-64ff228ab4f6/configs/ac0f34f7-1efc-408c-8a7f-eaa2c9d2bb64/versions/1/last_deployed", "result": "passed" }, "last_undeployed": { "job": { "id": "55ced596251e5fcfe86814d189da035e", "summary": { "version": "1.0.5", "plan_summary": {}, "apply_summary": {}, "destroy_summary": {}, "message_summary": {}, "plan_messages": {}, "apply_messages": {}, "destroy_messages": {} } }, "href": "https://projects.api.cloud.ibm.com/v1/projects/606bdec6-3b18-4c5e-9cf5-64ff228ab4f6/configs/ac0f34f7-1efc-408c-8a7f-eaa2c9d2bb64/versions/1/last_undeployed", "result": "failed" }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "version": 2, "is_draft": true, "outputs": [ { "name": "resource_group_id" }, { "name": "logdna_id" }, { "name": "sysdig_id" } ], "schematics": { "workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139", "validate_pre_script": { "type": "ansible", "path": "scripts/validate-pre-ansible-playbook.yaml", "short_description": "pre-validate" }, "validate_post_script": { "type": "ansible", "path": "scripts/validate-post-ansible-playbook.yaml", "short_description": "post validate" } }, "state": "draft", "update_available": true, "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/b0c44146-1ef6-40c2-82ba-74d51149770a", "deployment_mode": "project_deployed" }
The example response to a request for a resource configuration.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "shared-resources-dev", "description": "The shared resources that are used in dev environments.", "labels": [ "dev" ], "type": "manual", "resource_crns": [ "crn:v1:staging:public:continuous-delivery:us-south:a/d11256044e024d5bbea1a7d7ee4575c3:e988fcf7-2bd7-46de-a72d-339ebe859a9e::", "crn:v1:staging:public:toolchain:us-south:a/d11256044e024d5bbea1a7d7ee4575c3:618c70c7-0ead-40fb-86ce-e3f7b10c9f99::" ], "authorizations": { "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" } }, "active_draft": { "version": 2, "state": "draft", "href": "/v1/projects/db268db0-160b-4911-8f93-89659000a927/configs/9c7afed6-17fb-4c56-a13d-440a78f936bd/versions/2" }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "version": 1, "is_draft": true, "needs_attention_state": [], "outputs": [], "state": "apply_failed", "created_at": "2023-02-22T19:51:23.253Z", "updated_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/293c3c36-a094-4115-a12b-de0a9ca39be5", "deployment_mode": "user_deployed" }
The example response to a request for a resource configuration.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "shared-resources-dev", "description": "The shared resources that are used in dev environments.", "labels": [ "dev" ], "type": "manual", "resource_crns": [ "crn:v1:staging:public:continuous-delivery:us-south:a/d11256044e024d5bbea1a7d7ee4575c3:e988fcf7-2bd7-46de-a72d-339ebe859a9e::", "crn:v1:staging:public:toolchain:us-south:a/d11256044e024d5bbea1a7d7ee4575c3:618c70c7-0ead-40fb-86ce-e3f7b10c9f99::" ], "authorizations": { "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" } }, "active_draft": { "version": 2, "state": "draft", "href": "/v1/projects/db268db0-160b-4911-8f93-89659000a927/configs/9c7afed6-17fb-4c56-a13d-440a78f936bd/versions/2" }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "version": 1, "is_draft": true, "needs_attention_state": [], "outputs": [], "state": "apply_failed", "created_at": "2023-02-22T19:51:23.253Z", "updated_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/293c3c36-a094-4115-a12b-de0a9ca39be5", "deployment_mode": "user_deployed" }
Sample response to consume a stack.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "stack-config-example", "description": "A deployable architecture stack that substitutes the first member in a stack for another existing configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "region": "us-south", "resource_group_name": "stack-rg" }, "members": [ { "name": "foundation-deployable-architecture", "config_id": "293c3c36-a094-4115-a12b-de0a9ca39beX" }, { "name": "middleware-architecture", "config_id": "293c3c36-a094-4115-a12b-de0a9ca39beZ" } ] }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "version": 1, "is_draft": true, "state": "draft", "needs_attention_state": [], "outputs": [ { "name": "workload_cluster_server_url" } ], "created_at": "2023-02-22T19:51:23.253Z", "updated_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/293c3c36-a094-4115-a12b-de0a9ca39be5" }
Sample response to consume a stack.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "stack-config-example", "description": "A deployable architecture stack that substitutes the first member in a stack for another existing configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "region": "us-south", "resource_group_name": "stack-rg" }, "members": [ { "name": "foundation-deployable-architecture", "config_id": "293c3c36-a094-4115-a12b-de0a9ca39beX" }, { "name": "middleware-architecture", "config_id": "293c3c36-a094-4115-a12b-de0a9ca39beZ" } ] }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "version": 1, "is_draft": true, "state": "draft", "needs_attention_state": [], "outputs": [ { "name": "workload_cluster_server_url" } ], "created_at": "2023-02-22T19:51:23.253Z", "updated_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/293c3c36-a094-4115-a12b-de0a9ca39be5" }
Update a configuration
Update a configuration in a project by specifying the ID. Learn more.
Update a configuration in a project by specifying the ID. Learn more.
Update a configuration in a project by specifying the ID. Learn more.
Update a configuration in a project by specifying the ID. Learn more.
PATCH /v1/projects/{project_id}/configs/{id}
update_config(
self,
project_id: str,
id: str,
definition: 'ProjectConfigDefinitionPatch',
**kwargs,
) -> DetailedResponse
updateConfig(params)
(project *ProjectV1) UpdateConfig(updateConfigOptions *UpdateConfigOptions) (result *ProjectConfig, response *core.DetailedResponse, err error)
(project *ProjectV1) UpdateConfigWithContext(ctx context.Context, updateConfigOptions *UpdateConfigOptions) (result *ProjectConfig, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the UpdateConfigOptions
struct and set the fields to provide parameter values for the UpdateConfig
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The request body for the change delta of the project configuration to update.
An example of a request to update the configuration inputs.
{
"definition": {
"name": "env-stage",
"inputs": {
"account_id": "account_id",
"resource_group": "stage",
"access_tags": [
"env:stage"
],
"logdna_name": "LogDNA_stage_service",
"sysdig_name": "SysDig_stage_service"
}
}
}
An example of a request to update the configuration inputs.
{
"definition": {
"resource_crns": [
"crn:v1:staging:public:toolchain:us-south:a/d11256044e024d5bbea1a7d7ee4575c3:618c70c7-0ead-40fb-86ce-e3f7b10c9f99::"
]
}
}
An example of a request to update the configuration inputs.
{
"definition": {
"name": "env-stage",
"members": [
{
"name": "foundation-deployable-architecture",
"config_id": "293c3c36-a094-4115-a12b-de0a9ca39beX"
},
{
"name": "middleware-architecture",
"config_id": "293c3c36-a094-4115-a12b-de0a9ca39be5"
}
],
"inputs": {
"account_id": "account_id",
"resource_group": "stage"
}
}
}
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The name and description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Allowable values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Allowable values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The name and description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Allowable values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Allowable values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The UpdateConfig options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The name and description of a project configuration.
- Definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- ComplianceProfile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Allowable values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- Authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Allowable values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
curl -X PATCH --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" --header "Content-Type: application/json" --data '{ "definition": { "name": "env-stage", "inputs": { "account_id": "account_id", "resource_group": "stage", "access_tags": [ "env:stage" ], "logdna_name": "LogDNA_stage_service", "sysdig_name": "SysDig_stage_service" } } }' "{base_url}/v1/projects/{project_id}/configs/{id}"
projectConfigDefinitionPatchModel := &projectv1.ProjectConfigDefinitionPatchDAConfigDefinitionPropertiesPatch{ Name: core.StringPtr("env-stage"), } updateConfigOptions := projectService.NewUpdateConfigOptions( projectIdLink, configIdLink, projectConfigDefinitionPatchModel, ) projectConfig, response, err := projectService.UpdateConfig(updateConfigOptions) if err != nil { panic(err) } b, _ := json.MarshalIndent(projectConfig, "", " ") fmt.Println(string(b))
// Request models needed by this operation. // ProjectConfigDefinitionPatchDAConfigDefinitionPropertiesPatch const projectConfigDefinitionPatchModel = { name: 'env-stage', inputs: { account_id: 'account_id', resource_group: 'stage', access_tags: ['env:stage'], logdna_name: 'LogDNA_stage_service', sysdig_name: 'SysDig_stage_service' }, }; const params = { projectId: projectIdLink, id: configIdLink, definition: projectConfigDefinitionPatchModel, }; let res; try { res = await projectService.updateConfig(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
project_config_definition_patch_model = { 'name': 'env-stage', 'inputs': {'account_id': 'account_id', 'resource_group': 'stage', 'access_tags': ['env:stage'], 'logdna_name': 'LogDNA_stage_service', 'sysdig_name': 'SysDig_stage_service'}, } response = project_service.update_config( project_id=project_id_link, id=config_id_link, definition=project_config_definition_patch_model, ) project_config = response.get_result() print(json.dumps(project_config, indent=2))
Response
The standard schema of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
The project that is referenced by this resource.
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(http(s)?:\/\/)[a-zA-Z0-9\$\-_\.+!\*'\(\),=&?\/]+$
The last approved metadata of the configuration.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The href and results from the last action job that is performed on the project configuration.
The href and results from the last action job that is performed on the project configuration.
The href and results from the last action job that is performed on the project configuration.
The summary from the last monitoring action job that is performed on the project configuration.
The references that are used in the configuration to resolve input values.
- references
A Schematics workspace that is associated to a project configuration, with scripts.
The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The stack config parent of which this configuration is a member of.
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]A summary of a project configuration version.
A summary of a project configuration version.
The standard schema of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- needs_attention_state
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- last_approved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_validated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- cost_estimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- cra_logs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_deployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- last_undeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- last_monitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- drift_detection
A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- member_of
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A summary of a project configuration version.
- approved_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A summary of a project configuration version.
- deployed_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The standard schema of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- needs_attention_state
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- last_approved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_validated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- cost_estimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- cra_logs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_deployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- last_undeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- last_monitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- drift_detection
A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- member_of
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A summary of a project configuration version.
- approved_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A summary of a project configuration version.
- deployed_version
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The standard schema of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- NeedsAttentionState
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- LastApproved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- LastValidated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- CostEstimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- CraLogs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- Summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- LastDeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- LastUndeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- LastMonitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- DriftDetection
A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- Outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- Project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- Definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- Schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- ValidatePreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- ValidatePostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- DeployPreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- DeployPostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- UndeployPreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- UndeployPostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- MemberOf
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- Definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- Members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- Definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- ComplianceProfile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- Authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A summary of a project configuration version.
- ApprovedVersion
A summary of the definition in a project configuration version.
- Definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A summary of a project configuration version.
- DeployedVersion
A summary of the definition in a project configuration version.
- Definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
Status Code
The request was successful.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The example response to a request for a deployable architecture configuration draft.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "env-stage", "description": "The stage environment configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "ref:/configs/account-stage/inputs/account_id", "resource_group": "stage", "access_tags": [ "env:stage" ], "logdna_name": "The name of the LogDNA stage service instance.", "sysdig_name": "The name of the SysDig stage service instance." } }, "is_draft": true, "version": 2, "outputs": [ { "name": "resource_group_id" }, { "name": "logdna_id" }, { "name": "sysdig_id" } ], "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "schematics": { "workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139" }, "state": "validated", "update_available": true, "needs_attention_state": [], "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/b0c44146-1ef6-40c2-82ba-74d51149770a", "deployment_mode": "project_deployed" }
The example response to a request for a deployable architecture configuration draft.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "env-stage", "description": "The stage environment configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "ref:/configs/account-stage/inputs/account_id", "resource_group": "stage", "access_tags": [ "env:stage" ], "logdna_name": "The name of the LogDNA stage service instance.", "sysdig_name": "The name of the SysDig stage service instance." } }, "is_draft": true, "version": 2, "outputs": [ { "name": "resource_group_id" }, { "name": "logdna_id" }, { "name": "sysdig_id" } ], "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "schematics": { "workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139" }, "state": "validated", "update_available": true, "needs_attention_state": [], "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/b0c44146-1ef6-40c2-82ba-74d51149770a", "deployment_mode": "project_deployed" }
The example response to a request for a resource configuration draft.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "shared-resources-dev", "description": "The shared resources for dev environments.", "labels": [ "dev" ], "type": "manual", "resource_crns": [ "crn:v1:staging:public:toolchain:us-south:a/d11256044e024d5bbea1a7d7ee4575c3:618c70c7-0ead-40fb-86ce-e3f7b10c9f99::" ] }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "is_draft": false, "version": 2, "state": "applied", "needs_attention_state": [], "outputs": [], "created_at": "2023-02-22T19:51:23.253Z", "updated_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/293c3c36-a094-4115-a12b-de0a9ca39be5", "deployment_mode": "user_deployed" }
The example response to a request for a resource configuration draft.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "shared-resources-dev", "description": "The shared resources for dev environments.", "labels": [ "dev" ], "type": "manual", "resource_crns": [ "crn:v1:staging:public:toolchain:us-south:a/d11256044e024d5bbea1a7d7ee4575c3:618c70c7-0ead-40fb-86ce-e3f7b10c9f99::" ] }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "is_draft": false, "version": 2, "state": "applied", "needs_attention_state": [], "outputs": [], "created_at": "2023-02-22T19:51:23.253Z", "updated_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/293c3c36-a094-4115-a12b-de0a9ca39be5", "deployment_mode": "user_deployed" }
Sample response to create a stack.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "stack-bottom-up-example", "description": "A deployable architecture stack that includes two member deployable architectures.", "members": [ { "name": "foundation-deployable-architecture", "config_id": "293c3c36-a094-4115-a12b-de0a9ca39beX" }, { "name": "middleware-architecture", "config_id": "293c3c36-a094-4115-a12b-de0a9ca39be5" } ] }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "version": 1, "is_draft": true, "state": "draft", "needs_attention_state": [], "outputs": [], "created_at": "2023-02-22T19:51:23.253Z", "updated_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/293c3c36-a094-4115-a12b-de0a9ca39be5" }
Sample response to create a stack.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "stack-bottom-up-example", "description": "A deployable architecture stack that includes two member deployable architectures.", "members": [ { "name": "foundation-deployable-architecture", "config_id": "293c3c36-a094-4115-a12b-de0a9ca39beX" }, { "name": "middleware-architecture", "config_id": "293c3c36-a094-4115-a12b-de0a9ca39be5" } ] }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "version": 1, "is_draft": true, "state": "draft", "needs_attention_state": [], "outputs": [], "created_at": "2023-02-22T19:51:23.253Z", "updated_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/293c3c36-a094-4115-a12b-de0a9ca39be5" }
Delete a configuration
Delete a configuration in a project by specifying its ID.
Delete a configuration in a project by specifying its ID.
Delete a configuration in a project by specifying its ID.
Delete a configuration in a project by specifying its ID.
DELETE /v1/projects/{project_id}/configs/{id}
delete_config(
self,
project_id: str,
id: str,
**kwargs,
) -> DetailedResponse
deleteConfig(params)
(project *ProjectV1) DeleteConfig(deleteConfigOptions *DeleteConfigOptions) (result *ProjectConfigDelete, response *core.DetailedResponse, err error)
(project *ProjectV1) DeleteConfigWithContext(ctx context.Context, deleteConfigOptions *DeleteConfigOptions) (result *ProjectConfigDelete, response *core.DetailedResponse, err error)
Request
Instantiate the DeleteConfigOptions
struct and set the fields to provide parameter values for the DeleteConfig
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The DeleteConfig options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
curl -X DELETE --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" "{base_url}/v1/projects/{project_id}/configs/{id}"
deleteConfigOptions := projectService.NewDeleteConfigOptions( projectIdLink, configIdLink, ) projectConfigDelete, response, err := projectService.DeleteConfig(deleteConfigOptions) if err != nil { panic(err) } b, _ := json.MarshalIndent(projectConfigDelete, "", " ") fmt.Println(string(b))
const params = { projectId: projectIdLink, id: configIdLink, }; let res; try { res = await projectService.deleteConfig(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
response = project_service.delete_config( project_id=project_id_link, id=config_id_link, ) project_config_delete = response.get_result() print(json.dumps(project_config_delete, indent=2))
Response
The ID of the deleted configuration.
The ID of the deleted project or configuration.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The ID of the deleted configuration.
The ID of the deleted project or configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The ID of the deleted configuration.
The ID of the deleted project or configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The ID of the deleted configuration.
The ID of the deleted project or configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
Status Code
The request was successful.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The example response to a request to delete a configuration.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5" }
The example response to a request to delete a configuration.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5" }
Update a configuration to dev mode
Update a project configuration to development mode.
POST /v1/projects/{project_id}/configs/{id}/dev
Authentication
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Response
Status Code
The request was successful but the response is empty.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters that are in your request.
The credentials are invalid or authentication is required to succeed.
No Sample Response
Get a diff summary of a project configuration
Retrieve a diff summary of the specified project configuration between its current draft and the active version of a specific project.
GET /v1/projects/{project_id}/configs/{id}/diff
Authentication
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Response
The diff summary of the project configuration.
Status Code
The request was successful.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters that are in your request.
The credentials are invalid or authentication is required to succeed.
The example response to a request for a deployable architecture configuration diff summary.
{ "added": { "inputs": [ { "name": "account_id", "type": "string", "new_value": "5addba84e3f845be9acc27edee75a145" } ] }, "changed": { "inputs": [ { "name": "ibm_cloud_api_key", "type": "string", "new_value": "6c573253f969440ebd113fa3bf688809", "old_value": "9f100bfc7ef245119581a4aa4b4dc53a" }, { "name": "region", "type": "string", "new_value": "us-south", "old_value": "us-east" } ] }, "removed": { "inputs": [ { "name": "env", "type": "string", "old_value": "stage" } ] } }
The example response to a request for a resource configuration diff summary.
{ "added": { "resource_crns": [ "crn:v1:staging:public:continuous-delivery:us-south:a/d11256044e024d5bbea1a7d7ee4575c3:e988fcf7-2bd7-46de-a72d-339ebe859a9e::" ] }, "removed": { "resource_crns": [ "crn:v1:staging:public:toolchain:us-south:a/d11256044e024d5bbea1a7d7ee4575c3:618c70c7-0ead-40fb-86ce-e3f7b10c9f99::" ] }, "changed": { "resource_crns": null } }
Force approve a project configuration
Force approve configuration edits to the main configuration with an approving comment.
Force approve configuration edits to the main configuration with an approving comment.
Force approve configuration edits to the main configuration with an approving comment.
Force approve configuration edits to the main configuration with an approving comment.
POST /v1/projects/{project_id}/configs/{id}/force_approve
force_approve(
self,
project_id: str,
id: str,
comment: str,
**kwargs,
) -> DetailedResponse
forceApprove(params)
(project *ProjectV1) ForceApprove(forceApproveOptions *ForceApproveOptions) (result *ProjectConfigVersion, response *core.DetailedResponse, err error)
(project *ProjectV1) ForceApproveWithContext(ctx context.Context, forceApproveOptions *ForceApproveOptions) (result *ProjectConfigVersion, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the ForceApproveOptions
struct and set the fields to provide parameter values for the ForceApprove
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The comment to support the force approve action.
{
"comment": "Approving the changes"
}
Notes on the project draft action. If this action is a force approve on the draft configuration, you must include a nonempty comment.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
^(?!\s)(?!.*\s$)[^\x00-\x1F]+$
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
Notes on the project draft action. If this action is a force approve on the draft configuration, you must include a nonempty comment.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
Examples:
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
Notes on the project draft action. If this action is a force approve on the draft configuration, you must include a nonempty comment.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
Examples:
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The ForceApprove options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
Notes on the project draft action. If this action is a force approve on the draft configuration, you must include a nonempty comment.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
Examples:Approving the changes
curl -X POST --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" --header "Content-Type: application/json" --data '{ "comment": "Approving the changes" }' "{base_url}/v1/projects/{project_id}/configs/{id}/force_approve"
forceApproveOptions := projectService.NewForceApproveOptions( projectIdLink, configIdLink, "Approving the changes", ) projectConfigVersion, response, err := projectService.ForceApprove(forceApproveOptions) if err != nil { panic(err) } b, _ := json.MarshalIndent(projectConfigVersion, "", " ") fmt.Println(string(b))
const params = { projectId: projectIdLink, id: configIdLink, comment: 'Approving the changes', }; let res; try { res = await projectService.forceApprove(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
response = project_service.force_approve( project_id=project_id_link, id=config_id_link, comment='Approving the changes', ) project_config_version = response.get_result() print(json.dumps(project_config_version, indent=2))
Response
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
The project that is referenced by this resource.
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(http(s)?:\/\/)[a-zA-Z0-9\$\-_\.+!\*'\(\),=&?\/]+$
The last approved metadata of the configuration.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The href and results from the last action job that is performed on the project configuration.
The href and results from the last action job that is performed on the project configuration.
The href and results from the last action job that is performed on the project configuration.
The summary from the last monitoring action job that is performed on the project configuration.
The references that are used in the configuration to resolve input values.
- references
A Schematics workspace that is associated to a project configuration, with scripts.
The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The stack config parent of which this configuration is a member of.
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- needs_attention_state
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- last_approved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_validated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- cost_estimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- cra_logs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_deployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- last_undeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- last_monitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- drift_detection
A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- member_of
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- needs_attention_state
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- last_approved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_validated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- cost_estimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- cra_logs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_deployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- last_undeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- last_monitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- drift_detection
A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- member_of
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- NeedsAttentionState
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- LastApproved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- LastValidated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- CostEstimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- CraLogs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- Summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- LastDeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- LastUndeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- LastMonitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- DriftDetection
A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- Outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- Project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- Definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- Schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- ValidatePreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- ValidatePostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- DeployPreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- DeployPostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- UndeployPreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- UndeployPostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- MemberOf
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- Definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- Members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- Definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- ComplianceProfile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- Authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
Status Code
You successfully force approved a project configuration.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters that are in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The example response to a request for a deployable architecture configuration draft.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "env-stage", "description": "The stage environment configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "ref:/configs/account-stage/inputs/account_id", "resource_group": "stage", "access_tags": [ "env:stage" ], "logdna_name": "The name of the LogDNA stage service instance.", "sysdig_name": "The name of the SysDig stage service instance." } }, "is_draft": true, "version": 2, "outputs": [ { "name": "resource_group_id" }, { "name": "logdna_id" }, { "name": "sysdig_id" } ], "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "schematics": { "workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139" }, "state": "validated", "update_available": true, "needs_attention_state": [], "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/b0c44146-1ef6-40c2-82ba-74d51149770a", "deployment_mode": "project_deployed" }
The example response to a request for a deployable architecture configuration draft.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "env-stage", "description": "The stage environment configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "ref:/configs/account-stage/inputs/account_id", "resource_group": "stage", "access_tags": [ "env:stage" ], "logdna_name": "The name of the LogDNA stage service instance.", "sysdig_name": "The name of the SysDig stage service instance." } }, "is_draft": true, "version": 2, "outputs": [ { "name": "resource_group_id" }, { "name": "logdna_id" }, { "name": "sysdig_id" } ], "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "schematics": { "workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139" }, "state": "validated", "update_available": true, "needs_attention_state": [], "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/b0c44146-1ef6-40c2-82ba-74d51149770a", "deployment_mode": "project_deployed" }
Approve and merge a configuration draft
Approve and merge configuration edits to the main configuration.
Approve and merge configuration edits to the main configuration.
Approve and merge configuration edits to the main configuration.
Approve and merge configuration edits to the main configuration.
POST /v1/projects/{project_id}/configs/{id}/approve
approve(
self,
project_id: str,
id: str,
*,
comment: Optional[str] = None,
**kwargs,
) -> DetailedResponse
approve(params)
(project *ProjectV1) Approve(approveOptions *ApproveOptions) (result *ProjectConfigVersion, response *core.DetailedResponse, err error)
(project *ProjectV1) ApproveWithContext(ctx context.Context, approveOptions *ApproveOptions) (result *ProjectConfigVersion, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the ApproveOptions
struct and set the fields to provide parameter values for the Approve
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The comment to support the approve action.
{
"comment": "Approving the changes"
}
Notes on the project draft action. If this action is a force approve on the draft configuration, you must include a nonempty comment.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
^(?!\s)(?!.*\s$)[^\x00-\x1F]+$
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
Notes on the project draft action. If this action is a force approve on the draft configuration, you must include a nonempty comment.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
Examples:
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
Notes on the project draft action. If this action is a force approve on the draft configuration, you must include a nonempty comment.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
Examples:
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The Approve options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
Notes on the project draft action. If this action is a force approve on the draft configuration, you must include a nonempty comment.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
Examples:Approving the changes
curl -X POST --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" --header "Content-Type: application/json" --data '{ "comment": "Approving the changes" }' "{base_url}/v1/projects/{project_id}/configs/{id}/approve"
approveOptions := projectService.NewApproveOptions( projectIdLink, configIdLink, ) approveOptions.SetComment("Approving the changes") projectConfigVersion, response, err := projectService.Approve(approveOptions) if err != nil { panic(err) } b, _ := json.MarshalIndent(projectConfigVersion, "", " ") fmt.Println(string(b))
const params = { projectId: projectIdLink, id: configIdLink, comment: 'Approving the changes', }; let res; try { res = await projectService.approve(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
response = project_service.approve( project_id=project_id_link, id=config_id_link, comment='Approving the changes', ) project_config_version = response.get_result() print(json.dumps(project_config_version, indent=2))
Response
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
The project that is referenced by this resource.
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(http(s)?:\/\/)[a-zA-Z0-9\$\-_\.+!\*'\(\),=&?\/]+$
The last approved metadata of the configuration.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The href and results from the last action job that is performed on the project configuration.
The href and results from the last action job that is performed on the project configuration.
The href and results from the last action job that is performed on the project configuration.
The summary from the last monitoring action job that is performed on the project configuration.
The references that are used in the configuration to resolve input values.
- references
A Schematics workspace that is associated to a project configuration, with scripts.
The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The stack config parent of which this configuration is a member of.
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- needs_attention_state
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- last_approved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_validated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- cost_estimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- cra_logs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_deployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- last_undeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- last_monitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- drift_detection
A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- member_of
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- needs_attention_state
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- last_approved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_validated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- cost_estimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- cra_logs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_deployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- last_undeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- last_monitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- drift_detection
A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- member_of
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- NeedsAttentionState
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- LastApproved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- LastValidated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- CostEstimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- CraLogs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- Summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- LastDeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- LastUndeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- LastMonitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- DriftDetection
A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- Outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- Project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- Definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- Schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- ValidatePreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- ValidatePostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- DeployPreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- DeployPostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- UndeployPreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- UndeployPostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- MemberOf
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- Definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- Members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- Definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- ComplianceProfile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- Authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
Status Code
You successfully approved and merged a configuration draft.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The example response to a request for a deployable architecture configuration draft.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "env-stage", "description": "The stage environment configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "ref:/configs/account-stage/inputs/account_id", "resource_group": "stage", "access_tags": [ "env:stage" ], "logdna_name": "The name of the LogDNA stage service instance.", "sysdig_name": "The name of the SysDig stage service instance." } }, "is_draft": true, "version": 2, "outputs": [ { "name": "resource_group_id" }, { "name": "logdna_id" }, { "name": "sysdig_id" } ], "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "schematics": { "workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139" }, "state": "validated", "update_available": true, "needs_attention_state": [], "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/b0c44146-1ef6-40c2-82ba-74d51149770a", "deployment_mode": "project_deployed" }
The example response to a request for a deployable architecture configuration draft.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "env-stage", "description": "The stage environment configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "ref:/configs/account-stage/inputs/account_id", "resource_group": "stage", "access_tags": [ "env:stage" ], "logdna_name": "The name of the LogDNA stage service instance.", "sysdig_name": "The name of the SysDig stage service instance." } }, "is_draft": true, "version": 2, "outputs": [ { "name": "resource_group_id" }, { "name": "logdna_id" }, { "name": "sysdig_id" } ], "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "schematics": { "workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139" }, "state": "validated", "update_available": true, "needs_attention_state": [], "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/b0c44146-1ef6-40c2-82ba-74d51149770a", "deployment_mode": "project_deployed" }
Run a validation check
Run a validation check on a specific configuration in the project. The check includes creating or updating the associated Schematics workspace with a plan job, running the CRA scans, and cost estimation.
Run a validation check on a specific configuration in the project. The check includes creating or updating the associated Schematics workspace with a plan job, running the CRA scans, and cost estimation.
Run a validation check on a specific configuration in the project. The check includes creating or updating the associated Schematics workspace with a plan job, running the CRA scans, and cost estimation.
Run a validation check on a specific configuration in the project. The check includes creating or updating the associated Schematics workspace with a plan job, running the CRA scans, and cost estimation.
POST /v1/projects/{project_id}/configs/{id}/validate
validate_config(
self,
project_id: str,
id: str,
**kwargs,
) -> DetailedResponse
validateConfig(params)
(project *ProjectV1) ValidateConfig(validateConfigOptions *ValidateConfigOptions) (result *ProjectConfigVersion, response *core.DetailedResponse, err error)
(project *ProjectV1) ValidateConfigWithContext(ctx context.Context, validateConfigOptions *ValidateConfigOptions) (result *ProjectConfigVersion, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the ValidateConfigOptions
struct and set the fields to provide parameter values for the ValidateConfig
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The ValidateConfig options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
curl -X POST --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" "{base_url}/v1/projects/{project_id}/configs/{id}/validate"
validateConfigOptions := projectService.NewValidateConfigOptions( projectIdLink, configIdLink, ) projectConfigVersion, response, err := projectService.ValidateConfig(validateConfigOptions) if err != nil { panic(err) } b, _ := json.MarshalIndent(projectConfigVersion, "", " ") fmt.Println(string(b))
const params = { projectId: projectIdLink, id: configIdLink, }; let res; try { res = await projectService.validateConfig(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
response = project_service.validate_config( project_id=project_id_link, id=config_id_link, ) project_config_version = response.get_result() print(json.dumps(project_config_version, indent=2))
Response
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
The project that is referenced by this resource.
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(http(s)?:\/\/)[a-zA-Z0-9\$\-_\.+!\*'\(\),=&?\/]+$
The last approved metadata of the configuration.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The href and results from the last action job that is performed on the project configuration.
The href and results from the last action job that is performed on the project configuration.
The href and results from the last action job that is performed on the project configuration.
The summary from the last monitoring action job that is performed on the project configuration.
The references that are used in the configuration to resolve input values.
- references
A Schematics workspace that is associated to a project configuration, with scripts.
The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The stack config parent of which this configuration is a member of.
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- needs_attention_state
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- last_approved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_validated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- cost_estimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- cra_logs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_deployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- last_undeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- last_monitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- drift_detection
A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- member_of
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- needs_attention_state
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- last_approved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_validated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- cost_estimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- cra_logs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_deployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- last_undeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- last_monitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- drift_detection
A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- member_of
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- NeedsAttentionState
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- LastApproved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- LastValidated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- CostEstimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- CraLogs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- Summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- LastDeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- LastUndeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- LastMonitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- DriftDetection
A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- Outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- Project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- Definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- Schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- ValidatePreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- ValidatePostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- DeployPreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- DeployPostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- UndeployPreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- UndeployPostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- MemberOf
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- Definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- Members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- Definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- ComplianceProfile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- Authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
Status Code
The server successfully accepted the request to process the resource.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The request cannot be processed because of a conflict between the request and the current client-controlled state in the system.
The example response to a request for a deployable architecture configuration draft.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "env-stage", "description": "The stage environment configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "ref:/configs/account-stage/inputs/account_id", "resource_group": "stage", "access_tags": [ "env:stage" ], "logdna_name": "The name of the LogDNA stage service instance.", "sysdig_name": "The name of the SysDig stage service instance." } }, "is_draft": true, "version": 2, "outputs": [ { "name": "resource_group_id" }, { "name": "logdna_id" }, { "name": "sysdig_id" } ], "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "schematics": { "workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139" }, "state": "validated", "update_available": true, "needs_attention_state": [], "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/b0c44146-1ef6-40c2-82ba-74d51149770a", "deployment_mode": "project_deployed" }
The example response to a request for a deployable architecture configuration draft.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "env-stage", "description": "The stage environment configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "ref:/configs/account-stage/inputs/account_id", "resource_group": "stage", "access_tags": [ "env:stage" ], "logdna_name": "The name of the LogDNA stage service instance.", "sysdig_name": "The name of the SysDig stage service instance." } }, "is_draft": true, "version": 2, "outputs": [ { "name": "resource_group_id" }, { "name": "logdna_id" }, { "name": "sysdig_id" } ], "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "schematics": { "workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139" }, "state": "validated", "update_available": true, "needs_attention_state": [], "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/b0c44146-1ef6-40c2-82ba-74d51149770a", "deployment_mode": "project_deployed" }
Deploy a configuration
Deploy a project's configuration. This operation is asynchronous and can be tracked by using the get project configuration API with full metadata.
Deploy a project's configuration. This operation is asynchronous and can be tracked by using the get project configuration API with full metadata.
Deploy a project's configuration. This operation is asynchronous and can be tracked by using the get project configuration API with full metadata.
Deploy a project's configuration. This operation is asynchronous and can be tracked by using the get project configuration API with full metadata.
POST /v1/projects/{project_id}/configs/{id}/deploy
deploy_config(
self,
project_id: str,
id: str,
**kwargs,
) -> DetailedResponse
deployConfig(params)
(project *ProjectV1) DeployConfig(deployConfigOptions *DeployConfigOptions) (result *ProjectConfigVersion, response *core.DetailedResponse, err error)
(project *ProjectV1) DeployConfigWithContext(ctx context.Context, deployConfigOptions *DeployConfigOptions) (result *ProjectConfigVersion, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the DeployConfigOptions
struct and set the fields to provide parameter values for the DeployConfig
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The DeployConfig options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
curl -X POST --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" "{base_url}/v1/projects/{project_id}/configs/{id}/deploy"
deployConfigOptions := projectService.NewDeployConfigOptions( projectIdLink, configIdLink, ) projectConfigVersion, response, err := projectService.DeployConfig(deployConfigOptions) if err != nil { panic(err) } b, _ := json.MarshalIndent(projectConfigVersion, "", " ") fmt.Println(string(b))
const params = { projectId: projectIdLink, id: configIdLink, }; let res; try { res = await projectService.deployConfig(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
response = project_service.deploy_config( project_id=project_id_link, id=config_id_link, ) project_config_version = response.get_result() print(json.dumps(project_config_version, indent=2))
Response
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
The project that is referenced by this resource.
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(http(s)?:\/\/)[a-zA-Z0-9\$\-_\.+!\*'\(\),=&?\/]+$
The last approved metadata of the configuration.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The href and results from the last action job that is performed on the project configuration.
The href and results from the last action job that is performed on the project configuration.
The href and results from the last action job that is performed on the project configuration.
The summary from the last monitoring action job that is performed on the project configuration.
The references that are used in the configuration to resolve input values.
- references
A Schematics workspace that is associated to a project configuration, with scripts.
The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The stack config parent of which this configuration is a member of.
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- needs_attention_state
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- last_approved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_validated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- cost_estimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- cra_logs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_deployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- last_undeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- last_monitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- drift_detection
A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- member_of
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- needs_attention_state
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- last_approved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_validated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- cost_estimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- cra_logs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_deployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- last_undeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- last_monitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- drift_detection
A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- member_of
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- NeedsAttentionState
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- LastApproved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- LastValidated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- CostEstimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- CraLogs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- Summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- LastDeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- LastUndeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- LastMonitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- DriftDetection
A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- Outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- Project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- Definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- Schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- ValidatePreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- ValidatePostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- DeployPreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- DeployPostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- UndeployPreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- UndeployPostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- MemberOf
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- Definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- Members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- Definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- ComplianceProfile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- Authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
Status Code
The server successfully accepted the request to process the resource.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The request cannot be processed because of a conflict between the request and the current client-controlled state in the system.
The example response to a request for a deployable architecture configuration draft.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "env-stage", "description": "The stage environment configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "ref:/configs/account-stage/inputs/account_id", "resource_group": "stage", "access_tags": [ "env:stage" ], "logdna_name": "The name of the LogDNA stage service instance.", "sysdig_name": "The name of the SysDig stage service instance." } }, "is_draft": true, "version": 2, "outputs": [ { "name": "resource_group_id" }, { "name": "logdna_id" }, { "name": "sysdig_id" } ], "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "schematics": { "workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139" }, "state": "validated", "update_available": true, "needs_attention_state": [], "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/b0c44146-1ef6-40c2-82ba-74d51149770a", "deployment_mode": "project_deployed" }
The example response to a request for a deployable architecture configuration draft.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "env-stage", "description": "The stage environment configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "ref:/configs/account-stage/inputs/account_id", "resource_group": "stage", "access_tags": [ "env:stage" ], "logdna_name": "The name of the LogDNA stage service instance.", "sysdig_name": "The name of the SysDig stage service instance." } }, "is_draft": true, "version": 2, "outputs": [ { "name": "resource_group_id" }, { "name": "logdna_id" }, { "name": "sysdig_id" } ], "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "schematics": { "workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139" }, "state": "validated", "update_available": true, "needs_attention_state": [], "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/b0c44146-1ef6-40c2-82ba-74d51149770a", "deployment_mode": "project_deployed" }
Undeploy configuration resources
Undeploy a project's configuration resources. The operation undeploys all the resources that are deployed with the specific configuration. You can track it by using the get project configuration API with full metadata.
Undeploy a project's configuration resources. The operation undeploys all the resources that are deployed with the specific configuration. You can track it by using the get project configuration API with full metadata.
Undeploy a project's configuration resources. The operation undeploys all the resources that are deployed with the specific configuration. You can track it by using the get project configuration API with full metadata.
Undeploy a project's configuration resources. The operation undeploys all the resources that are deployed with the specific configuration. You can track it by using the get project configuration API with full metadata.
POST /v1/projects/{project_id}/configs/{id}/undeploy
undeploy_config(
self,
project_id: str,
id: str,
**kwargs,
) -> DetailedResponse
undeployConfig(params)
(project *ProjectV1) UndeployConfig(undeployConfigOptions *UndeployConfigOptions) (result *ProjectConfigVersion, response *core.DetailedResponse, err error)
(project *ProjectV1) UndeployConfigWithContext(ctx context.Context, undeployConfigOptions *UndeployConfigOptions) (result *ProjectConfigVersion, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the UndeployConfigOptions
struct and set the fields to provide parameter values for the UndeployConfig
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The UndeployConfig options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
curl -X POST --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" "{base_url}/v1/projects/{project_id}/configs/{id}/undeploy"
undeployConfigOptions := projectService.NewUndeployConfigOptions( projectIdLink, configIdLink, ) projectConfigVersion, response, err := projectService.UndeployConfig(undeployConfigOptions) if err != nil { panic(err) } b, _ := json.MarshalIndent(projectConfigVersion, "", " ") fmt.Println(string(b))
const params = { projectId: projectIdLink, id: configIdLink, }; let res; try { res = await projectService.undeployConfig(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
response = project_service.undeploy_config( project_id=project_id_link, id=config_id_link, ) project_config_version = response.get_result() print(json.dumps(project_config_version, indent=2))
Response
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
The project that is referenced by this resource.
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(http(s)?:\/\/)[a-zA-Z0-9\$\-_\.+!\*'\(\),=&?\/]+$
The last approved metadata of the configuration.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The href and results from the last action job that is performed on the project configuration.
The href and results from the last action job that is performed on the project configuration.
The href and results from the last action job that is performed on the project configuration.
The summary from the last monitoring action job that is performed on the project configuration.
The references that are used in the configuration to resolve input values.
- references
A Schematics workspace that is associated to a project configuration, with scripts.
The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The stack config parent of which this configuration is a member of.
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- needs_attention_state
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- last_approved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_validated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- cost_estimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- cra_logs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_deployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- last_undeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- last_monitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- drift_detection
A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- member_of
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- needs_attention_state
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- last_approved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_validated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- cost_estimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- cra_logs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_deployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- last_undeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- last_monitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- drift_detection
A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- member_of
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- NeedsAttentionState
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- LastApproved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- LastValidated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- CostEstimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- CraLogs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- Summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- LastDeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- LastUndeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- LastMonitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- DriftDetection
A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- Outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- Project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- Definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- Schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- ValidatePreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- ValidatePostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- DeployPreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- DeployPostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- UndeployPreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- UndeployPostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- MemberOf
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- Definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- Members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- Definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- ComplianceProfile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- Authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
Status Code
The server successfully accepted the request to process the resource.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The request cannot be processed because of a conflict between the request and the current client-controlled state in the system.
The example response to a request for a deployable architecture configuration draft.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "env-stage", "description": "The stage environment configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "ref:/configs/account-stage/inputs/account_id", "resource_group": "stage", "access_tags": [ "env:stage" ], "logdna_name": "The name of the LogDNA stage service instance.", "sysdig_name": "The name of the SysDig stage service instance." } }, "is_draft": true, "version": 2, "outputs": [ { "name": "resource_group_id" }, { "name": "logdna_id" }, { "name": "sysdig_id" } ], "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "schematics": { "workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139" }, "state": "validated", "update_available": true, "needs_attention_state": [], "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/b0c44146-1ef6-40c2-82ba-74d51149770a", "deployment_mode": "project_deployed" }
The example response to a request for a deployable architecture configuration draft.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "env-stage", "description": "The stage environment configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "ref:/configs/account-stage/inputs/account_id", "resource_group": "stage", "access_tags": [ "env:stage" ], "logdna_name": "The name of the LogDNA stage service instance.", "sysdig_name": "The name of the SysDig stage service instance." } }, "is_draft": true, "version": 2, "outputs": [ { "name": "resource_group_id" }, { "name": "logdna_id" }, { "name": "sysdig_id" } ], "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "schematics": { "workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139" }, "state": "validated", "update_available": true, "needs_attention_state": [], "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/b0c44146-1ef6-40c2-82ba-74d51149770a", "deployment_mode": "project_deployed" }
Sync a project configuration
Sync a project configuration by analyzing the associated pipeline runs and Schematics workspace logs to get the configuration back to a working state.
Sync a project configuration by analyzing the associated pipeline runs and Schematics workspace logs to get the configuration back to a working state.
Sync a project configuration by analyzing the associated pipeline runs and Schematics workspace logs to get the configuration back to a working state.
Sync a project configuration by analyzing the associated pipeline runs and Schematics workspace logs to get the configuration back to a working state.
POST /v1/projects/{project_id}/configs/{id}/sync
sync_config(
self,
project_id: str,
id: str,
*,
schematics: Optional['SchematicsWorkspace'] = None,
**kwargs,
) -> DetailedResponse
syncConfig(params)
(project *ProjectV1) SyncConfig(syncConfigOptions *SyncConfigOptions) (response *core.DetailedResponse, err error)
(project *ProjectV1) SyncConfigWithContext(ctx context.Context, syncConfigOptions *SyncConfigOptions) (response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the SyncConfigOptions
struct and set the fields to provide parameter values for the SyncConfig
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
An optional Schematics workspace to be used by this configuration.
{
"schematics": {
"workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139"
}
}
A Schematics workspace to use for deploying this deployable architecture.
If you are importing data from an existing Schematics workspace that is not backed by cart, then you must provide a
locator_id
. If you are using a Schematics workspace that is backed by cart, alocator_id
is not required because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
code is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace.
For more information, see Creating workspaces and importing your Terraform template.
- If only a
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A Schematics workspace to use for deploying this deployable architecture.
If you are importing data from an existing Schematics workspace that is not backed by cart, then you must provide a
locator_id
. If you are using a Schematics workspace that is backed by cart, alocator_id
is not required because the Schematics workspace has one. There are 3 scenarios:- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
code is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information, see Creating workspaces and importing your Terraform template.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
- If only a
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A Schematics workspace to use for deploying this deployable architecture.
If you are importing data from an existing Schematics workspace that is not backed by cart, then you must provide a
locator_id
. If you are using a Schematics workspace that is backed by cart, alocator_id
is not required because the Schematics workspace has one. There are 3 scenarios:- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
code is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information, see Creating workspaces and importing your Terraform template.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
- If only a
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The SyncConfig options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A Schematics workspace to use for deploying this deployable architecture.
If you are importing data from an existing Schematics workspace that is not backed by cart, then you must provide a
locator_id
. If you are using a Schematics workspace that is backed by cart, alocator_id
is not required because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
code is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace.
For more information, see Creating workspaces and importing your Terraform template.
Examples:{ "workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139" }
- Schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
- If only a
curl -X POST --location --header "Authorization: Bearer {iam_token}" --header "Content-Type: application/json" --data '{ "schematics": { "workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139" } }' "{base_url}/v1/projects/{project_id}/configs/{id}/sync"
schematicsWorkspaceModel := &projectv1.SchematicsWorkspace{ WorkspaceCrn: core.StringPtr("crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139"), } syncConfigOptions := projectService.NewSyncConfigOptions( projectIdLink, configIdLink, ) syncConfigOptions.SetSchematics(schematicsWorkspaceModel) response, err := projectService.SyncConfig(syncConfigOptions) if err != nil { panic(err) } if response.StatusCode != 204 { fmt.Printf("\nUnexpected response status code received from SyncConfig(): %d\n", response.StatusCode) }
// Request models needed by this operation. // SchematicsWorkspace const schematicsWorkspaceModel = { workspace_crn: 'crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139', }; const params = { projectId: projectIdLink, id: configIdLink, schematics: schematicsWorkspaceModel, }; try { await projectService.syncConfig(params); } catch (err) { console.warn(err); }
schematics_workspace_model = { 'workspace_crn': 'crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139', } response = project_service.sync_config( project_id=project_id_link, id=config_id_link, schematics=schematics_workspace_model, )
Response
Status Code
The request was successful but the response is empty.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The request cannot be processed because of a conflict between the request and the current client-controlled state in the system.
No Sample Response
List all deployed resources
List resources that are deployed by a configuration.
List resources that are deployed by a configuration.
List resources that are deployed by a configuration.
List resources that are deployed by a configuration.
GET /v1/projects/{project_id}/configs/{id}/resources
list_config_resources(
self,
project_id: str,
id: str,
**kwargs,
) -> DetailedResponse
listConfigResources(params)
(project *ProjectV1) ListConfigResources(listConfigResourcesOptions *ListConfigResourcesOptions) (result *ProjectConfigResourceCollection, response *core.DetailedResponse, err error)
(project *ProjectV1) ListConfigResourcesWithContext(ctx context.Context, listConfigResourcesOptions *ListConfigResourcesOptions) (result *ProjectConfigResourceCollection, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the ListConfigResourcesOptions
struct and set the fields to provide parameter values for the ListConfigResources
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The ListConfigResources options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
curl -X GET --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" "{base_url}/v1/projects/{project_id}/configs/{id}/resources"
listConfigResourcesOptions := projectService.NewListConfigResourcesOptions( projectIdLink, configIdLink, ) projectConfigResourceCollection, response, err := projectService.ListConfigResources(listConfigResourcesOptions) if err != nil { panic(err) } b, _ := json.MarshalIndent(projectConfigResourceCollection, "", " ") fmt.Println(string(b))
const params = { projectId: projectIdLink, id: configIdLink, }; let res; try { res = await projectService.listConfigResources(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
response = project_service.list_config_resources( project_id=project_id_link, id=config_id_link, ) project_config_resource_collection = response.get_result() print(json.dumps(project_config_resource_collection, indent=2))
Response
The project configuration resource list.
The collection list operation response schema that defines the array property with the name
resources
.Possible values: 0 ≤ number of items ≤ 1000
The total number of resources that are deployed by the configuration.
The project configuration resource list.
The collection list operation response schema that defines the array property with the name
resources
.Possible values: 0 ≤ number of items ≤ 1000
- resources
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The name of the resource.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).*$/
The resource type.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).*$/
The flag that indicates whether the status of the resource is tainted.
The resource group of the resource.
Possible values: length ≥ 0, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The total number of resources that are deployed by the configuration.
The project configuration resource list.
The collection list operation response schema that defines the array property with the name
resources
.Possible values: 0 ≤ number of items ≤ 1000
- resources
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The name of the resource.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).*$/
The resource type.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).*$/
The flag that indicates whether the status of the resource is tainted.
The resource group of the resource.
Possible values: length ≥ 0, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The total number of resources that are deployed by the configuration.
The project configuration resource list.
The collection list operation response schema that defines the array property with the name
resources
.Possible values: 0 ≤ number of items ≤ 1000
- Resources
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The name of the resource.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).*$/
The resource type.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).*$/
The flag that indicates whether the status of the resource is tainted.
The resource group of the resource.
Possible values: length ≥ 0, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]*$/
The total number of resources that are deployed by the configuration.
Status Code
You successfully retrieved the deployed resources.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The example response to a request to get project configuration resources.
{ "resources": [ { "resource_crn": "crn:v1:staging:public:toolchain:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::", "resource_name": "toolchain_instance", "resource_type": "ibm_cd_toolchain", "resource_tainted": false, "resource_group_name": "" }, { "resource_crn": "crn:v1:staging:public:cloud-object-storage:global:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::", "resource_name": "cos_bucket_instance", "resource_type": "ibm_cos_bucket", "resource_tainted": false, "resource_group_name": "" } ], "resources_count": 2 }
The example response to a request to get project configuration resources.
{ "resources": [ { "resource_crn": "crn:v1:staging:public:toolchain:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::", "resource_name": "toolchain_instance", "resource_type": "ibm_cd_toolchain", "resource_tainted": false, "resource_group_name": "" }, { "resource_crn": "crn:v1:staging:public:cloud-object-storage:global:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::", "resource_name": "cos_bucket_instance", "resource_type": "ibm_cos_bucket", "resource_tainted": false, "resource_group_name": "" } ], "resources_count": 2 }
Create a stack definition
Defines inputs at the stack level that users need to configure along with input values at the member level. These values are included in the catalog entry when the deployable architecture stack is exported to a private catalog and are required for the deployable architecture stack to deploy. You can add a reference to a value, or add the value explicitly at the member level.
Defines inputs at the stack level that users need to configure along with input values at the member level. These values are included in the catalog entry when the deployable architecture stack is exported to a private catalog and are required for the deployable architecture stack to deploy. You can add a reference to a value, or add the value explicitly at the member level.
Defines inputs at the stack level that users need to configure along with input values at the member level. These values are included in the catalog entry when the deployable architecture stack is exported to a private catalog and are required for the deployable architecture stack to deploy. You can add a reference to a value, or add the value explicitly at the member level.
Defines inputs at the stack level that users need to configure along with input values at the member level. These values are included in the catalog entry when the deployable architecture stack is exported to a private catalog and are required for the deployable architecture stack to deploy. You can add a reference to a value, or add the value explicitly at the member level.
POST /v1/projects/{project_id}/configs/{id}/stack_definition
create_stack_definition(
self,
project_id: str,
id: str,
stack_definition: 'StackDefinitionBlockPrototype',
**kwargs,
) -> DetailedResponse
createStackDefinition(params)
(project *ProjectV1) CreateStackDefinition(createStackDefinitionOptions *CreateStackDefinitionOptions) (result *StackDefinition, response *core.DetailedResponse, err error)
(project *ProjectV1) CreateStackDefinitionWithContext(ctx context.Context, createStackDefinitionOptions *CreateStackDefinitionOptions) (result *StackDefinition, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the CreateStackDefinitionOptions
struct and set the fields to provide parameter values for the CreateStackDefinition
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The new stack definition document.
Sample request to create a stack definition.
{
"stack_definition": {
"inputs": [
{
"name": "region",
"type": "string",
"required": true,
"default": "us-south",
"hidden": false
},
{
"name": "resource_group",
"type": "string",
"default": "Default"
}
],
"outputs": [
{
"name": "vpc_cluster_id",
"value": "cluster_id"
}
]
}
}
The definition block for a stack definition.
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition block for a stack definition.
- stack_definition
Defines the inputs that users need to configure at the stack level. These inputs are included in the catalog entry when the deployable architecture stack is exported to a private catalog.
Possible values: 0 ≤ number of items ≤ 100
- inputs
The stack definition input name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The variable type.
Allowable values: [
array
,boolean
,float
,int
,number
,password
,string
,object
]The description of the variable.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
A boolean value to denote if the property is required.
A boolean value to denote whether the property is hidden, as in not exposed to the user.
The outputs associated with this stack definition.
Possible values: 0 ≤ number of items ≤ 100
- outputs
The stack definition output name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition block for a stack definition.
- stackDefinition
Defines the inputs that users need to configure at the stack level. These inputs are included in the catalog entry when the deployable architecture stack is exported to a private catalog.
Possible values: 0 ≤ number of items ≤ 100
- inputs
The stack definition input name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The variable type.
Allowable values: [
array
,boolean
,float
,int
,number
,password
,string
,object
]The description of the variable.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
A boolean value to denote if the property is required.
A boolean value to denote whether the property is hidden, as in not exposed to the user.
The outputs associated with this stack definition.
Possible values: 0 ≤ number of items ≤ 100
- outputs
The stack definition output name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The CreateStackDefinition options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition block for a stack definition.
Examples:{ "inputs": [ { "name": "region", "type": "string", "required": true, "default": "us-south", "hidden": false }, { "name": "resource_group", "type": "string", "default": "Default" } ], "outputs": [ { "name": "vpc_cluster_id", "value": "cluster_id" } ] }
- StackDefinition
Defines the inputs that users need to configure at the stack level. These inputs are included in the catalog entry when the deployable architecture stack is exported to a private catalog.
Possible values: 0 ≤ number of items ≤ 100
- Inputs
The stack definition input name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The variable type.
Allowable values: [
array
,boolean
,float
,int
,number
,password
,string
,object
]The description of the variable.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
A boolean value to denote if the property is required.
A boolean value to denote whether the property is hidden, as in not exposed to the user.
The outputs associated with this stack definition.
Possible values: 0 ≤ number of items ≤ 100
- Outputs
The stack definition output name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
curl -X POST --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" --header "Content-Type: application/json" --data '{ "stack_definition": { "inputs": [ { "name": "region", "type": "string", "required": true, "default": "us-south", "hidden": false }, { "name": "resource_group", "type": "string", "default": "Default" } ], "outputs": [ { "name": "vpc_cluster_id", "value": "cluster_id" } ], "members": [ { "name": "foundation-deployable-architecture", "inputs": [ { "name": "region" }, { "name": "cluster_name" } ] }, { "name": "middleware-architecture", "inputs": [ { "name": "kube_version" } ] } ] } }' "{base_url}/v1/projects/{project_id}/configs/{id}/stack_definition"
// Request models needed by this operation. // StackDefinitionInputVariable const stackDefinitionInputVariableModel = { name: 'region', type: 'string', default: 'us-south', required: true, hidden: false, }; // StackDefinitionOutputVariable const stackDefinitionOutputVariableModel = { name: 'vpc_cluster_id', value: 'cluster_id', }; // StackDefinitionBlockPrototype const stackDefinitionBlockPrototypeModel = { inputs: [stackDefinitionInputVariableModel], outputs: [stackDefinitionOutputVariableModel], }; const params = { projectId: projectIdLink, id: configIdLink, stackDefinition: stackDefinitionBlockPrototypeModel, }; let res; try { res = await projectService.createStackDefinition(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
stack_definition_input_variable_model = { 'name': 'region', 'type': 'string', 'default': 'us-south', 'required': True, 'hidden': False, } stack_definition_output_variable_model = { 'name': 'vpc_cluster_id', 'value': 'cluster_id', } stack_definition_block_prototype_model = { 'inputs': [stack_definition_input_variable_model], 'outputs': [stack_definition_output_variable_model], } response = project_service.create_stack_definition( project_id=project_id_link, id=config_id_link, stack_definition=stack_definition_block_prototype_model, ) stack_definition = response.get_result() print(json.dumps(stack_definition, indent=2))
Response
The stack definition.
The definition block for a stack definition.
The ID of the stack definition.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The state for the stack definition
Possible values: [
draft
,published
]The configuration reference.
- configuration
The definition of the config reference
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(http(s)?:\/\/)[a-zA-Z0-9\$\-_\.+!\*'\(\),=&?\/]+$
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(http(s)?:\/\/)[a-zA-Z0-9\$\-_\.+!\*'\(\),=&?\/]+$
The stack definition.
The ID of the stack definition.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The state for the stack definition.
Possible values: [
draft
,published
]The configuration reference.
- configuration
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the config reference.
- definition
The name of the configuration.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition block for a stack definition.
- stack_definition
Defines the inputs that users need to configure at the stack level. These inputs are included in the catalog entry when the deployable architecture stack is exported to a private catalog.
Possible values: 0 ≤ number of items ≤ 100
- inputs
The stack definition input name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The variable type.
Possible values: [
array
,boolean
,float
,int
,number
,password
,string
,object
]The description of the variable.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
A boolean value to denote if the property is required.
A boolean value to denote whether the property is hidden, as in not exposed to the user.
The outputs associated with this stack definition.
Possible values: 0 ≤ number of items ≤ 100
- outputs
The stack definition output name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 500
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The version locator of the member deployable architecture.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
The member inputs to use for the stack definition.
Possible values: 0 ≤ number of items ≤ 100
- inputs
The member input name to use.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
The stack definition.
The ID of the stack definition.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The state for the stack definition.
Possible values: [
draft
,published
]The configuration reference.
- configuration
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the config reference.
- definition
The name of the configuration.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition block for a stack definition.
- stack_definition
Defines the inputs that users need to configure at the stack level. These inputs are included in the catalog entry when the deployable architecture stack is exported to a private catalog.
Possible values: 0 ≤ number of items ≤ 100
- inputs
The stack definition input name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The variable type.
Possible values: [
array
,boolean
,float
,int
,number
,password
,string
,object
]The description of the variable.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
A boolean value to denote if the property is required.
A boolean value to denote whether the property is hidden, as in not exposed to the user.
The outputs associated with this stack definition.
Possible values: 0 ≤ number of items ≤ 100
- outputs
The stack definition output name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 500
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The version locator of the member deployable architecture.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
The member inputs to use for the stack definition.
Possible values: 0 ≤ number of items ≤ 100
- inputs
The member input name to use.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
The stack definition.
The ID of the stack definition.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The state for the stack definition.
Possible values: [
draft
,published
]The configuration reference.
- Configuration
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the config reference.
- Definition
The name of the configuration.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition block for a stack definition.
- StackDefinition
Defines the inputs that users need to configure at the stack level. These inputs are included in the catalog entry when the deployable architecture stack is exported to a private catalog.
Possible values: 0 ≤ number of items ≤ 100
- Inputs
The stack definition input name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The variable type.
Possible values: [
array
,boolean
,float
,int
,number
,password
,string
,object
]The description of the variable.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
A boolean value to denote if the property is required.
A boolean value to denote whether the property is hidden, as in not exposed to the user.
The outputs associated with this stack definition.
Possible values: 0 ≤ number of items ≤ 100
- Outputs
The stack definition output name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 500
- Members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The version locator of the member deployable architecture.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
The member inputs to use for the stack definition.
Possible values: 0 ≤ number of items ≤ 100
- Inputs
The member input name to use.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
Status Code
The new resource was created.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
Sample response from a create stack template operation.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca6678a", "stack_definition": { "inputs": [ { "name": "region", "type": "string", "required": true, "default": "us-south", "hidden": false }, { "name": "resource_group", "type": "string", "default": "Default" } ], "outputs": [ { "name": "vpc_cluster_id", "value": "cluster_id" } ], "members": [ { "name": "foundation-deployable-architecture", "version_locator": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": [ { "name": "region", "value": "us-south" }, { "name": "cluster_name", "value": "foundation-cluster" } ] }, { "name": "middleware-architecture", "version_locator": "01e1a9ad-534b-4ab9-996a-b8f2a8653d5c.4d86732e-04b9-4dab-bfdc-5b514d86ecd8", "inputs": [ { "name": "kube_version", "value": 1.29 } ] } ] }, "state": "draft", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "configuration": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "stack-bottom-up-example" }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/template" }
Sample response from a create stack template operation.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca6678a", "stack_definition": { "inputs": [ { "name": "region", "type": "string", "required": true, "default": "us-south", "hidden": false }, { "name": "resource_group", "type": "string", "default": "Default" } ], "outputs": [ { "name": "vpc_cluster_id", "value": "cluster_id" } ], "members": [ { "name": "foundation-deployable-architecture", "version_locator": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": [ { "name": "region", "value": "us-south" }, { "name": "cluster_name", "value": "foundation-cluster" } ] }, { "name": "middleware-architecture", "version_locator": "01e1a9ad-534b-4ab9-996a-b8f2a8653d5c.4d86732e-04b9-4dab-bfdc-5b514d86ecd8", "inputs": [ { "name": "kube_version", "value": 1.29 } ] } ] }, "state": "draft", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "configuration": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "stack-bottom-up-example" }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/template" }
Get a stack definition
Retrieve the stack definition that is associated to the configuration.
Retrieve the stack definition that is associated to the configuration.
Retrieve the stack definition that is associated to the configuration.
Retrieve the stack definition that is associated to the configuration.
GET /v1/projects/{project_id}/configs/{id}/stack_definition
get_stack_definition(
self,
project_id: str,
id: str,
**kwargs,
) -> DetailedResponse
getStackDefinition(params)
(project *ProjectV1) GetStackDefinition(getStackDefinitionOptions *GetStackDefinitionOptions) (result *StackDefinition, response *core.DetailedResponse, err error)
(project *ProjectV1) GetStackDefinitionWithContext(ctx context.Context, getStackDefinitionOptions *GetStackDefinitionOptions) (result *StackDefinition, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the GetStackDefinitionOptions
struct and set the fields to provide parameter values for the GetStackDefinition
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The GetStackDefinition options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
curl -X GET --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" "{base_url}/v1/projects/{project_id}/configs/{id}/stack_definition"
const params = { projectId: projectIdLink, id: configIdLink, }; let res; try { res = await projectService.getStackDefinition(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
response = project_service.get_stack_definition( project_id=project_id_link, id=config_id_link, ) stack_definition = response.get_result() print(json.dumps(stack_definition, indent=2))
Response
The stack definition.
The definition block for a stack definition.
The ID of the stack definition.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The state for the stack definition
Possible values: [
draft
,published
]The configuration reference.
- configuration
The definition of the config reference
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(http(s)?:\/\/)[a-zA-Z0-9\$\-_\.+!\*'\(\),=&?\/]+$
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(http(s)?:\/\/)[a-zA-Z0-9\$\-_\.+!\*'\(\),=&?\/]+$
The stack definition.
The ID of the stack definition.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The state for the stack definition.
Possible values: [
draft
,published
]The configuration reference.
- configuration
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the config reference.
- definition
The name of the configuration.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition block for a stack definition.
- stack_definition
Defines the inputs that users need to configure at the stack level. These inputs are included in the catalog entry when the deployable architecture stack is exported to a private catalog.
Possible values: 0 ≤ number of items ≤ 100
- inputs
The stack definition input name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The variable type.
Possible values: [
array
,boolean
,float
,int
,number
,password
,string
,object
]The description of the variable.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
A boolean value to denote if the property is required.
A boolean value to denote whether the property is hidden, as in not exposed to the user.
The outputs associated with this stack definition.
Possible values: 0 ≤ number of items ≤ 100
- outputs
The stack definition output name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 500
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The version locator of the member deployable architecture.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
The member inputs to use for the stack definition.
Possible values: 0 ≤ number of items ≤ 100
- inputs
The member input name to use.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
The stack definition.
The ID of the stack definition.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The state for the stack definition.
Possible values: [
draft
,published
]The configuration reference.
- configuration
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the config reference.
- definition
The name of the configuration.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition block for a stack definition.
- stack_definition
Defines the inputs that users need to configure at the stack level. These inputs are included in the catalog entry when the deployable architecture stack is exported to a private catalog.
Possible values: 0 ≤ number of items ≤ 100
- inputs
The stack definition input name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The variable type.
Possible values: [
array
,boolean
,float
,int
,number
,password
,string
,object
]The description of the variable.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
A boolean value to denote if the property is required.
A boolean value to denote whether the property is hidden, as in not exposed to the user.
The outputs associated with this stack definition.
Possible values: 0 ≤ number of items ≤ 100
- outputs
The stack definition output name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 500
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The version locator of the member deployable architecture.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
The member inputs to use for the stack definition.
Possible values: 0 ≤ number of items ≤ 100
- inputs
The member input name to use.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
The stack definition.
The ID of the stack definition.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The state for the stack definition.
Possible values: [
draft
,published
]The configuration reference.
- Configuration
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the config reference.
- Definition
The name of the configuration.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition block for a stack definition.
- StackDefinition
Defines the inputs that users need to configure at the stack level. These inputs are included in the catalog entry when the deployable architecture stack is exported to a private catalog.
Possible values: 0 ≤ number of items ≤ 100
- Inputs
The stack definition input name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The variable type.
Possible values: [
array
,boolean
,float
,int
,number
,password
,string
,object
]The description of the variable.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
A boolean value to denote if the property is required.
A boolean value to denote whether the property is hidden, as in not exposed to the user.
The outputs associated with this stack definition.
Possible values: 0 ≤ number of items ≤ 100
- Outputs
The stack definition output name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 500
- Members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The version locator of the member deployable architecture.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
The member inputs to use for the stack definition.
Possible values: 0 ≤ number of items ≤ 100
- Inputs
The member input name to use.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
Status Code
The new resource was created.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
Sample response from a create stack template operation.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca6678a", "stack_definition": { "inputs": [ { "name": "region", "type": "string", "required": true, "default": "us-south", "hidden": false }, { "name": "resource_group", "type": "string", "default": "Default" } ], "outputs": [ { "name": "vpc_cluster_id", "value": "cluster_id" } ], "members": [ { "name": "foundation-deployable-architecture", "version_locator": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": [ { "name": "region", "value": "us-south" }, { "name": "cluster_name", "value": "foundation-cluster" } ] }, { "name": "middleware-architecture", "version_locator": "01e1a9ad-534b-4ab9-996a-b8f2a8653d5c.4d86732e-04b9-4dab-bfdc-5b514d86ecd8", "inputs": [ { "name": "kube_version", "value": 1.29 } ] } ] }, "state": "draft", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "configuration": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "stack-bottom-up-example" }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/template" }
Sample response from a create stack template operation.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca6678a", "stack_definition": { "inputs": [ { "name": "region", "type": "string", "required": true, "default": "us-south", "hidden": false }, { "name": "resource_group", "type": "string", "default": "Default" } ], "outputs": [ { "name": "vpc_cluster_id", "value": "cluster_id" } ], "members": [ { "name": "foundation-deployable-architecture", "version_locator": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": [ { "name": "region", "value": "us-south" }, { "name": "cluster_name", "value": "foundation-cluster" } ] }, { "name": "middleware-architecture", "version_locator": "01e1a9ad-534b-4ab9-996a-b8f2a8653d5c.4d86732e-04b9-4dab-bfdc-5b514d86ecd8", "inputs": [ { "name": "kube_version", "value": 1.29 } ] } ] }, "state": "draft", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "configuration": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "stack-bottom-up-example" }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/template" }
Update a stack definition
Update the stack definition that is associated with the configuration.
Update the stack definition that is associated with the configuration.
Update the stack definition that is associated with the configuration.
Update the stack definition that is associated with the configuration.
PATCH /v1/projects/{project_id}/configs/{id}/stack_definition
update_stack_definition(
self,
project_id: str,
id: str,
stack_definition: 'StackDefinitionBlockPrototype',
**kwargs,
) -> DetailedResponse
updateStackDefinition(params)
(project *ProjectV1) UpdateStackDefinition(updateStackDefinitionOptions *UpdateStackDefinitionOptions) (result *StackDefinition, response *core.DetailedResponse, err error)
(project *ProjectV1) UpdateStackDefinitionWithContext(ctx context.Context, updateStackDefinitionOptions *UpdateStackDefinitionOptions) (result *StackDefinition, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the UpdateStackDefinitionOptions
struct and set the fields to provide parameter values for the UpdateStackDefinition
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The change delta of the stack definition to update.
Sample request to patch a stack template.
{
"stack_definition": {
"inputs": [
{
"name": "region",
"type": "string",
"required": true,
"default": "eu-gb",
"hidden": false
}
]
}
}
The definition block for a stack definition.
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition block for a stack definition.
- stack_definition
Defines the inputs that users need to configure at the stack level. These inputs are included in the catalog entry when the deployable architecture stack is exported to a private catalog.
Possible values: 0 ≤ number of items ≤ 100
- inputs
The stack definition input name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The variable type.
Allowable values: [
array
,boolean
,float
,int
,number
,password
,string
,object
]The description of the variable.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
A boolean value to denote if the property is required.
A boolean value to denote whether the property is hidden, as in not exposed to the user.
The outputs associated with this stack definition.
Possible values: 0 ≤ number of items ≤ 100
- outputs
The stack definition output name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition block for a stack definition.
- stackDefinition
Defines the inputs that users need to configure at the stack level. These inputs are included in the catalog entry when the deployable architecture stack is exported to a private catalog.
Possible values: 0 ≤ number of items ≤ 100
- inputs
The stack definition input name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The variable type.
Allowable values: [
array
,boolean
,float
,int
,number
,password
,string
,object
]The description of the variable.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
A boolean value to denote if the property is required.
A boolean value to denote whether the property is hidden, as in not exposed to the user.
The outputs associated with this stack definition.
Possible values: 0 ≤ number of items ≤ 100
- outputs
The stack definition output name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The UpdateStackDefinition options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition block for a stack definition.
Examples:{ "inputs": [ { "name": "region", "type": "string", "required": true, "default": "eu-gb", "hidden": false } ] }
- StackDefinition
Defines the inputs that users need to configure at the stack level. These inputs are included in the catalog entry when the deployable architecture stack is exported to a private catalog.
Possible values: 0 ≤ number of items ≤ 100
- Inputs
The stack definition input name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The variable type.
Allowable values: [
array
,boolean
,float
,int
,number
,password
,string
,object
]The description of the variable.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
A boolean value to denote if the property is required.
A boolean value to denote whether the property is hidden, as in not exposed to the user.
The outputs associated with this stack definition.
Possible values: 0 ≤ number of items ≤ 100
- Outputs
The stack definition output name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
curl -X PATCH --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" --header "Content-Type: application/json" --data '{ "stack_definition": { "inputs": [ { "name": "region", "type": "string", "required": true, "default": "eu-gb", "hidden": false } ], "members": [ { "name": "foundation-deployable-architecture", "inputs": [ { "name": "cluster_name" } ] } ] } }' "{base_url}/v1/projects/{project_id}/configs/{id}/stack_definition"
// Request models needed by this operation. // StackDefinitionInputVariable const stackDefinitionInputVariableModel = { name: 'region', type: 'string', default: 'eu-gb', required: true, hidden: false, }; // StackDefinitionBlockPrototype const stackDefinitionBlockPrototypeModel = { inputs: [stackDefinitionInputVariableModel], }; const params = { projectId: projectIdLink, id: configIdLink, stackDefinition: stackDefinitionBlockPrototypeModel, }; let res; try { res = await projectService.updateStackDefinition(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
stack_definition_input_variable_model = { 'name': 'region', 'type': 'string', 'default': 'eu-gb', 'required': True, 'hidden': False, } stack_definition_block_prototype_model = { 'inputs': [stack_definition_input_variable_model], } response = project_service.update_stack_definition( project_id=project_id_link, id=config_id_link, stack_definition=stack_definition_block_prototype_model, ) stack_definition = response.get_result() print(json.dumps(stack_definition, indent=2))
Response
The stack definition.
The definition block for a stack definition.
The ID of the stack definition.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The state for the stack definition
Possible values: [
draft
,published
]The configuration reference.
- configuration
The definition of the config reference
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(http(s)?:\/\/)[a-zA-Z0-9\$\-_\.+!\*'\(\),=&?\/]+$
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(http(s)?:\/\/)[a-zA-Z0-9\$\-_\.+!\*'\(\),=&?\/]+$
The stack definition.
The ID of the stack definition.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The state for the stack definition.
Possible values: [
draft
,published
]The configuration reference.
- configuration
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the config reference.
- definition
The name of the configuration.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition block for a stack definition.
- stack_definition
Defines the inputs that users need to configure at the stack level. These inputs are included in the catalog entry when the deployable architecture stack is exported to a private catalog.
Possible values: 0 ≤ number of items ≤ 100
- inputs
The stack definition input name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The variable type.
Possible values: [
array
,boolean
,float
,int
,number
,password
,string
,object
]The description of the variable.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
A boolean value to denote if the property is required.
A boolean value to denote whether the property is hidden, as in not exposed to the user.
The outputs associated with this stack definition.
Possible values: 0 ≤ number of items ≤ 100
- outputs
The stack definition output name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 500
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The version locator of the member deployable architecture.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
The member inputs to use for the stack definition.
Possible values: 0 ≤ number of items ≤ 100
- inputs
The member input name to use.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
The stack definition.
The ID of the stack definition.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The state for the stack definition.
Possible values: [
draft
,published
]The configuration reference.
- configuration
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the config reference.
- definition
The name of the configuration.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition block for a stack definition.
- stack_definition
Defines the inputs that users need to configure at the stack level. These inputs are included in the catalog entry when the deployable architecture stack is exported to a private catalog.
Possible values: 0 ≤ number of items ≤ 100
- inputs
The stack definition input name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The variable type.
Possible values: [
array
,boolean
,float
,int
,number
,password
,string
,object
]The description of the variable.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
A boolean value to denote if the property is required.
A boolean value to denote whether the property is hidden, as in not exposed to the user.
The outputs associated with this stack definition.
Possible values: 0 ≤ number of items ≤ 100
- outputs
The stack definition output name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 500
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The version locator of the member deployable architecture.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
The member inputs to use for the stack definition.
Possible values: 0 ≤ number of items ≤ 100
- inputs
The member input name to use.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
The stack definition.
The ID of the stack definition.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The state for the stack definition.
Possible values: [
draft
,published
]The configuration reference.
- Configuration
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the config reference.
- Definition
The name of the configuration.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition block for a stack definition.
- StackDefinition
Defines the inputs that users need to configure at the stack level. These inputs are included in the catalog entry when the deployable architecture stack is exported to a private catalog.
Possible values: 0 ≤ number of items ≤ 100
- Inputs
The stack definition input name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The variable type.
Possible values: [
array
,boolean
,float
,int
,number
,password
,string
,object
]The description of the variable.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
A boolean value to denote if the property is required.
A boolean value to denote whether the property is hidden, as in not exposed to the user.
The outputs associated with this stack definition.
Possible values: 0 ≤ number of items ≤ 100
- Outputs
The stack definition output name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 500
- Members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The version locator of the member deployable architecture.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
The member inputs to use for the stack definition.
Possible values: 0 ≤ number of items ≤ 100
- Inputs
The member input name to use.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
The value of the stack definition output.
Status Code
The request was successful.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
Sample response from a patch stack template operation.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca6678a", "stack_definition": { "inputs": [ { "name": "region", "type": "string", "required": true, "default": "eu-gb", "hidden": false } ], "outputs": [ { "name": "vpc_cluster_id", "value": "cluster_id" } ], "members": [ { "name": "foundation-deployable-architecture", "version_locator": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": [ { "name": "cluster_name", "value": "foundation-cluster" } ] } ] }, "state": "draft", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "configuration": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "stack-bottom-up-example" }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/template" }
Sample response from a patch stack template operation.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca6678a", "stack_definition": { "inputs": [ { "name": "region", "type": "string", "required": true, "default": "eu-gb", "hidden": false } ], "outputs": [ { "name": "vpc_cluster_id", "value": "cluster_id" } ], "members": [ { "name": "foundation-deployable-architecture", "version_locator": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": [ { "name": "cluster_name", "value": "foundation-cluster" } ] } ] }, "state": "draft", "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "configuration": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "stack-bottom-up-example" }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/template" }
Export a deployable architecture stack to the private catalog
Exports the deployable architecture stack to a private catalog. All member deployable architectures within the stack must be validated and deployed before the stack is exported. The stack definition must also exist before the stack is exported. You can export the stack as a new product, or as a new version of an existing product.
Exports the deployable architecture stack to a private catalog. All member deployable architectures within the stack must be validated and deployed before the stack is exported. The stack definition must also exist before the stack is exported. You can export the stack as a new product, or as a new version of an existing product.
Exports the deployable architecture stack to a private catalog. All member deployable architectures within the stack must be validated and deployed before the stack is exported. The stack definition must also exist before the stack is exported. You can export the stack as a new product, or as a new version of an existing product.
Exports the deployable architecture stack to a private catalog. All member deployable architectures within the stack must be validated and deployed before the stack is exported. The stack definition must also exist before the stack is exported. You can export the stack as a new product, or as a new version of an existing product.
POST /v1/projects/{project_id}/configs/{id}/stack_definition/export
export_stack_definition(
self,
project_id: str,
id: str,
settings: 'StackDefinitionExportRequest',
**kwargs,
) -> DetailedResponse
exportStackDefinition(params)
(project *ProjectV1) ExportStackDefinition(exportStackDefinitionOptions *ExportStackDefinitionOptions) (result *StackDefinitionExportResponse, response *core.DetailedResponse, err error)
(project *ProjectV1) ExportStackDefinitionWithContext(ctx context.Context, exportStackDefinitionOptions *ExportStackDefinitionOptions) (result *StackDefinitionExportResponse, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the ExportStackDefinitionOptions
struct and set the fields to provide parameter values for the ExportStackDefinition
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The payload for the private catalog export request.
Sample request to export a stack definition to a new product
{
"catalog_id": "01e1a9ad-534b-4ab9-996a-b8f2a8653d5c",
"label": "Stack Deployable Architecture"
}
The product label
Possible values: length ≤ 128, Value must match regular expression
^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$
The catalog ID to publish.
Possible values: length ≤ 36, Value must match regular expression
^[\-0-9a-zA-Z]+$
Tags associated with the catalog product
Possible values: 0 ≤ number of items ≤ 10, 1 ≤ length ≤ 32, Value must match regular expression
^[a-zA-Z0-9][a-zA-Z0-9-_]*$
The semver value of this new version of the product
Possible values: 5 ≤ length ≤ 60, Value must match regular expression
^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
The variation of this new version of the product
Possible values: length ≤ 128, Value must match regular expression
^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The payload for the stack definition export request to create a product.
- settings
The catalog ID to publish.
Possible values: length ≤ 36, Value must match regular expression
/^[\\-0-9a-zA-Z]+$/
The semver value of this new version of the product.
Possible values: 5 ≤ length ≤ 60, Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-((?:0|[1-9]\\d*|\\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\\.(?:0|[1-9]\\d*|\\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\\+([0-9a-zA-Z-]+(?:\\.[0-9a-zA-Z-]+)*))?$/
The variation of this new version of the product.
Possible values: length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The product label.
Possible values: length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
Tags associated with the catalog product.
Possible values: 0 ≤ number of items ≤ 10, 1 ≤ length ≤ 32, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_]*$/
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The payload for the stack definition export request to create a product.
- settings
The catalog ID to publish.
Possible values: length ≤ 36, Value must match regular expression
/^[\\-0-9a-zA-Z]+$/
The semver value of this new version of the product.
Possible values: 5 ≤ length ≤ 60, Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-((?:0|[1-9]\\d*|\\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\\.(?:0|[1-9]\\d*|\\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\\+([0-9a-zA-Z-]+(?:\\.[0-9a-zA-Z-]+)*))?$/
The variation of this new version of the product.
Possible values: length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The product label.
Possible values: length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
Tags associated with the catalog product.
Possible values: 0 ≤ number of items ≤ 10, 1 ≤ length ≤ 32, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_]*$/
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The ExportStackDefinition options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The payload for the stack definition export request to create a product.
- Settings
The catalog ID to publish.
Possible values: length ≤ 36, Value must match regular expression
/^[\\-0-9a-zA-Z]+$/
The semver value of this new version of the product.
Possible values: 5 ≤ length ≤ 60, Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-((?:0|[1-9]\\d*|\\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\\.(?:0|[1-9]\\d*|\\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\\+([0-9a-zA-Z-]+(?:\\.[0-9a-zA-Z-]+)*))?$/
The variation of this new version of the product.
Possible values: length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The product label.
Possible values: length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
Tags associated with the catalog product.
Possible values: 0 ≤ number of items ≤ 10, 1 ≤ length ≤ 32, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_]*$/
curl -X POST --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" --header "Content-Type: application/json" --data '{ "catalog_id": "01e1a9ad-534b-4ab9-996a-b8f2a8653d5c", "label": "Stack Deployable Architecture" }' "{base_url}/v1/projects/{project_id}/configs/{id}/stack_definition/export"
// Request models needed by this operation. // StackDefinitionExportRequestStackDefinitionExportCatalogRequest const stackDefinitionExportRequestModel = { catalog_id: '01e1a9ad-534b-4ab9-996a-b8f2a8653d5c', label: 'Stack Deployable Architecture', }; const params = { projectId: projectIdLink, id: configIdLink, settings: stackDefinitionExportRequestModel, }; let res; try { res = await projectService.exportStackDefinition(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
stack_definition_export_request_model = { 'catalog_id': '01e1a9ad-534b-4ab9-996a-b8f2a8653d5c', 'label': 'Stack Deployable Architecture', } response = project_service.export_stack_definition( project_id=project_id_link, id=config_id_link, settings=stack_definition_export_request_model, ) stack_definition_export_response = response.get_result() print(json.dumps(stack_definition_export_response, indent=2))
Response
The response to a successful template publish.
The catalog ID to publish.
Possible values: length ≤ 36, Value must match regular expression
^[\-0-9a-zA-Z]+$
The product ID to publish.
Possible values: length ≤ 36, Value must match regular expression
^[\-0-9a-zA-Z]+$
The version locator of the created deployable architecture.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
^(?!\s)(?!.*\s$)[\.0-9a-z-A-Z_-]+$
The product target kind value
Possible values: length ≤ 36, Value must match regular expression
^[\-0-9a-zA-Z]+$
The product format kind value
Possible values: length ≤ 36, Value must match regular expression
^[\-0-9a-zA-Z]+$
The payload for the stack definition export response.
The catalog ID to publish.
Possible values: length ≤ 36, Value must match regular expression
/^[\\-0-9a-zA-Z]+$/
The product ID to publish.
Possible values: length ≤ 36, Value must match regular expression
/^[\\-0-9a-zA-Z]+$/
The version locator of the created deployable architecture.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
The product target kind value.
Possible values: length ≤ 36, Value must match regular expression
/^[\\-0-9a-zA-Z]+$/
The product format kind value.
Possible values: length ≤ 36, Value must match regular expression
/^[\\-0-9a-zA-Z]+$/
The payload for the stack definition export response.
The catalog ID to publish.
Possible values: length ≤ 36, Value must match regular expression
/^[\\-0-9a-zA-Z]+$/
The product ID to publish.
Possible values: length ≤ 36, Value must match regular expression
/^[\\-0-9a-zA-Z]+$/
The version locator of the created deployable architecture.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
The product target kind value.
Possible values: length ≤ 36, Value must match regular expression
/^[\\-0-9a-zA-Z]+$/
The product format kind value.
Possible values: length ≤ 36, Value must match regular expression
/^[\\-0-9a-zA-Z]+$/
The payload for the stack definition export response.
The catalog ID to publish.
Possible values: length ≤ 36, Value must match regular expression
/^[\\-0-9a-zA-Z]+$/
The product ID to publish.
Possible values: length ≤ 36, Value must match regular expression
/^[\\-0-9a-zA-Z]+$/
The version locator of the created deployable architecture.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
The product target kind value.
Possible values: length ≤ 36, Value must match regular expression
/^[\\-0-9a-zA-Z]+$/
The product format kind value.
Possible values: length ≤ 36, Value must match regular expression
/^[\\-0-9a-zA-Z]+$/
Status Code
The request was successful.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
Sample response from exporting a stack definition to the private catalog
{ "catalog_id": "01e1a9ad-534b-4ab9-996a-b8f2a8653d5c", "product_id": "b60b5876-d074-478a-ac73-f979898c527b", "version_locator": "01e1a9ad-534b-4ab9-996a-b8f2a8653d5c.f9f73bdb-5c7d-4ea6-82ef-9debc6340df8", "kind": "terraform", "format": "stack" }
Sample response from exporting a stack definition to the private catalog
{ "catalog_id": "01e1a9ad-534b-4ab9-996a-b8f2a8653d5c", "product_id": "b60b5876-d074-478a-ac73-f979898c527b", "version_locator": "01e1a9ad-534b-4ab9-996a-b8f2a8653d5c.f9f73bdb-5c7d-4ea6-82ef-9debc6340df8", "kind": "terraform", "format": "stack" }
Get a list of project configuration versions
Retrieve a list of previous and current versions of a project configuration in a specific project.
Retrieve a list of previous and current versions of a project configuration in a specific project.
Retrieve a list of previous and current versions of a project configuration in a specific project.
Retrieve a list of previous and current versions of a project configuration in a specific project.
GET /v1/projects/{project_id}/configs/{id}/versions
list_config_versions(
self,
project_id: str,
id: str,
**kwargs,
) -> DetailedResponse
listConfigVersions(params)
(project *ProjectV1) ListConfigVersions(listConfigVersionsOptions *ListConfigVersionsOptions) (result *ProjectConfigVersionSummaryCollection, response *core.DetailedResponse, err error)
(project *ProjectV1) ListConfigVersionsWithContext(ctx context.Context, listConfigVersionsOptions *ListConfigVersionsOptions) (result *ProjectConfigVersionSummaryCollection, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the ListConfigVersionsOptions
struct and set the fields to provide parameter values for the ListConfigVersions
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The ListConfigVersions options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
curl -X GET --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" "{base_url}/v1/projects/{project_id}/configs/{id}/versions"
listConfigVersionsOptions := projectService.NewListConfigVersionsOptions( projectIdLink, configIdLink, ) projectConfigVersionSummaryCollection, response, err := projectService.ListConfigVersions(listConfigVersionsOptions) if err != nil { panic(err) } b, _ := json.MarshalIndent(projectConfigVersionSummaryCollection, "", " ") fmt.Println(string(b))
const params = { projectId: projectIdLink, id: configIdLink, }; let res; try { res = await projectService.listConfigVersions(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
response = project_service.list_config_versions( project_id=project_id_link, id=config_id_link, ) project_config_version_summary_collection = response.get_result() print(json.dumps(project_config_version_summary_collection, indent=2))
Response
The project configuration version list.
The collection list operation response schema that defines the array property with the name
versions
.Possible values: 0 ≤ number of items ≤ 1000
The project configuration version list.
The collection list operation response schema that defines the array property with the name
versions
.Possible values: 0 ≤ number of items ≤ 1000
- versions
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The project configuration version list.
The collection list operation response schema that defines the array property with the name
versions
.Possible values: 0 ≤ number of items ≤ 1000
- versions
A summary of the definition in a project configuration version.
- definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The project configuration version list.
The collection list operation response schema that defines the array property with the name
versions
.Possible values: 0 ≤ number of items ≤ 1000
- Versions
A summary of the definition in a project configuration version.
- Definition
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The version number of the configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
Status Code
You successfully retrieved the configuration versions.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The example response to a request to list project configuration drafts.
{ "versions": [ { "definition": { "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global" }, "version": 1, "state": "approved", "href": "https://projects.api.cloud.ibm.com/v1/projects/db268db0-160b-4911-8f93-89659000a927/configs/293c3c36-a094-4115-a12b-de0a9ca39be5/versions/1" }, { "definition": { "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global" }, "version": 2, "state": "validated", "href": "https://projects.api.cloud.ibm.com/v1/projects/db268db0-160b-4911-8f93-89659000a927/configs/293c3c36-a094-4115-a12b-de0a9ca39be5/versions/2" } ] }
The example response to a request to list project configuration drafts.
{ "versions": [ { "definition": { "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global" }, "version": 1, "state": "approved", "href": "https://projects.api.cloud.ibm.com/v1/projects/db268db0-160b-4911-8f93-89659000a927/configs/293c3c36-a094-4115-a12b-de0a9ca39be5/versions/1" }, { "definition": { "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global" }, "version": 2, "state": "validated", "href": "https://projects.api.cloud.ibm.com/v1/projects/db268db0-160b-4911-8f93-89659000a927/configs/293c3c36-a094-4115-a12b-de0a9ca39be5/versions/2" } ] }
Get a specific project configuration version
Retrieve a specific version of a configuration in a project.
Retrieve a specific version of a configuration in a project.
Retrieve a specific version of a configuration in a project.
Retrieve a specific version of a configuration in a project.
GET /v1/projects/{project_id}/configs/{id}/versions/{version}
get_config_version(
self,
project_id: str,
id: str,
version: int,
**kwargs,
) -> DetailedResponse
getConfigVersion(params)
(project *ProjectV1) GetConfigVersion(getConfigVersionOptions *GetConfigVersionOptions) (result *ProjectConfigVersion, response *core.DetailedResponse, err error)
(project *ProjectV1) GetConfigVersionWithContext(ctx context.Context, getConfigVersionOptions *GetConfigVersionOptions) (result *ProjectConfigVersion, response *core.DetailedResponse, err error)
Request
Instantiate the GetConfigVersionOptions
struct and set the fields to provide parameter values for the GetConfigVersion
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The configuration version.
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The configuration version.
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The configuration version.
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The GetConfigVersion options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The configuration version.
curl -X GET --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" "{base_url}/v1/projects/{project_id}/configs/{id}/versions/{version}"
getConfigVersionOptions := projectService.NewGetConfigVersionOptions( projectIdLink, configIdLink, int64(38), ) projectConfigVersion, response, err := projectService.GetConfigVersion(getConfigVersionOptions) if err != nil { panic(err) } b, _ := json.MarshalIndent(projectConfigVersion, "", " ") fmt.Println(string(b))
const params = { projectId: projectIdLink, id: configIdLink, version: 38, }; let res; try { res = await projectService.getConfigVersion(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
response = project_service.get_config_version( project_id=project_id_link, id=config_id_link, version=38, ) project_config_version = response.get_result() print(json.dumps(project_config_version, indent=2))
Response
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
The project that is referenced by this resource.
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(http(s)?:\/\/)[a-zA-Z0-9\$\-_\.+!\*'\(\),=&?\/]+$
The last approved metadata of the configuration.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The href and results from the last action job that is performed on the project configuration.
The href and results from the last action job that is performed on the project configuration.
The href and results from the last action job that is performed on the project configuration.
The summary from the last monitoring action job that is performed on the project configuration.
The references that are used in the configuration to resolve input values.
- references
A Schematics workspace that is associated to a project configuration, with scripts.
The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The stack config parent of which this configuration is a member of.
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- needs_attention_state
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- last_approved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_validated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- cost_estimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- cra_logs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_deployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- last_undeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- last_monitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- drift_detection
A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- member_of
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- needs_attention_state
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- last_approved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_validated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- cost_estimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- cra_logs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- last_deployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- last_undeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- pre_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- post_job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- project_error
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- last_monitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- drift_detection
A brief summary of an action.
- job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- plan_summary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- apply_summary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- destroy_summary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- message_summary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- plan_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- apply_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- success_messages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- destroy_messages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- validate_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- deploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_pre_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- undeploy_post_script
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- member_of
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- compliance_profile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
A specific version of a project configuration.
The ID of the configuration. If this parameter is empty, an ID is automatically created for the configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the configuration.
The flag that indicates whether the version of the configuration is draft, or active.
The needs attention state of a configuration.
Possible values: 0 ≤ number of items ≤ 50
- NeedsAttentionState
The id of the event.
The name of the event.
The severity of the event. This is a system generated field. For user triggered events the field is not present.
Possible values: [
INFO
,WARNING
,ERROR
]An actionable URL that users can access in response to the event. This is a system generated field. For user triggered events the field is not present.
The configuration id and version for which the event occurred. This field is only available for user generated events. For system triggered events the field is not present.
The IAM id of the user that triggered the event. This field is only available for user generated events. For system triggered events the field is not present.
The timestamp of the event.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The last approved metadata of the configuration.
- LastApproved
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The comment that is left by the user who approved the configuration.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]+$/
The flag that indicates whether the approval was forced approved.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- LastValidated
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The cost estimate of the configuration. This property exists only after the first configuration validation.
- CostEstimate
The version of the cost estimate of the configuration.
Possible values: Value must match regular expression
/^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-[\\da-zA-Z-]+)?(?:\\+[\\da-zA-Z-]+)?$/
The currency of the cost estimate of the configuration.
Possible values: [
USD
,usd
]The total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total hourly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The past total monthly cost estimate of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total hourly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
The difference between the current and past total monthly cost estimates of the configuration.
Possible values: Value must match regular expression
/^-?\\d+(\\.\\d+)?$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The Code Risk Analyzer logs of the configuration based on Code Risk Analyzer version 2.0.4.
- CraLogs
The version of the Code Risk Analyzer logs of the configuration. The metadata for this schema is specific to Code Risk Analyzer version 2.0.4.
Possible values: [
2.0.4
]The schema version of Code Risk Analyzer logs of the configuration.
The status of the Code Risk Analyzer logs of the configuration.
Possible values: [
passed
,failed
]The Code Risk Analyzer logs a summary of the configuration.
- Summary
The total number of Code Risk Analyzer rules that were applied in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that passed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that failed in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
The number of Code Risk Analyzer rules that were skipped in the scan.
Possible values: 1 ≤ length ≤ 10, Value must match regular expression
/^\\d+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The href and results from the last action job that is performed on the project configuration.
- LastDeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The href and results from the last action job that is performed on the project configuration.
- LastUndeployed
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
A brief summary of a pre- and post-action.
- PreJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
A brief summary of a pre- and post-action.
- PostJob
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A brief summary of a pre- and post-action job. This property is populated only after an action is run as part of a validation, deployment, or undeployment.
- Summary
The ID of the Schematics action job that ran as part of the pre- and post-job.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The number of tasks that were run in the job.
The number of tasks that successfully ran in the job.
The number of tasks that failed in the job.
The number of tasks that were skipped in the job.
The number of tasks that were changed in the job.
A system-level error from the pipeline that ran for this specific pre- and post-job.
- ProjectError
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
The ID of the user that triggered the pipeline that ran the pre- and post-job.
The HTTP status code for the error.
Possible values: Value must match regular expression
/^[1-5][0-9][0-9]$/
The summary description of the error.
The detailed message from the source error.
The summary from the last monitoring action job that is performed on the project configuration.
- LastMonitoring
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The result of the last action.
Possible values: [
failed
,passed
]The summary for drift detection jobs that are performed as part of the last monitoring action.
- DriftDetection
A brief summary of an action.
- Job
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The summaries of jobs that were performed on the configuration.
- Summary
The version of the job summary.
Possible values: 1 ≤ length ≤ 20, Value must match regular expression
/^(\\d+\\.)?(\\d+\\.)?(\\*|\\d+)$/
The summary of the plan jobs on the configuration.
- PlanSummary
The number of resources to be added. This property is reported only if Schematics triggered a terraform plan job.
The number of resources that failed during the plan job. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be updated. This property is reported only if Schematics triggered a Terraform plan job.
The number of resources to be destroyed. This property is reported only if Schematics triggered a Terraform plan job.
The collection of planned added resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed planned resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned updated resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of planned destroy resources. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the apply jobs on the configuration.
- ApplySummary
The number of applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The number of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
The collection of successfully applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed applied resources. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The summary of the destroy jobs on the configuration.
- DestroySummary
The number of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
The number of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
The summary of results from destroyed resources from the job. This property is reported only if Schematics triggered a Terraform destroy job.
- Resources
The collection of destroyed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of failed resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The collection of tainted resources. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The message summaries of jobs on the configuration.
- MessageSummary
The number of information messages. This property is reported only if Schematics triggered a Terraform job.
The number of debug messages. This property is reported only if Schematics triggered a Terraform job.
The number of error messages. This property is reported only if Schematics triggered a Terraform job.
The plan messages on the configuration.
- PlanMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of update messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The collection of destroy messages. This property is reported only if Schematics triggered a Terraform plan job.
Possible values: 0 ≤ number of items ≤ 50
The messages of apply jobs on the configuration.
- ApplyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
The collection of success messages. This property is reported only if Schematics triggered a Terraform apply job.
Possible values: 0 ≤ number of items ≤ 50
- SuccessMessages
The resource type.
The time that is taken.
The ID.
The messages of destroy jobs on the configuration.
- DestroyMessages
The collection of error messages. This property is reported only if Schematics triggered a Terraform destroy job.
Possible values: 0 ≤ number of items ≤ 50
The outputs of a Schematics template property.
Possible values: 0 ≤ number of items ≤ 50
- Outputs
The variable name.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(?!\\s)(?!.*\\s$).+$/
A short explanation of the output value.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
This property can be any value - a string, number, boolean, array, or object.
The project that is referenced by this resource.
- Project
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The definition of the project reference.
- Definition
The name of the project.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^'\"`<>{}\\x00-\\x1F]+$/
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
The references that are used in the configuration to resolve input values.
A Schematics workspace that is associated to a project configuration, with scripts.
- Schematics
An IBM Cloud resource name that uniquely identifies a resource.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
/(?!\\s)(?!.*\\s$)^(crn)[^'\"`<>{}\\s\\x00-\\x1F]*/
Examples:crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- ValidatePreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- ValidatePostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- DeployPreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- DeployPostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- UndeployPreScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
A script to be run as part of a project configuration for a specific stage (pre or post) and action (validate, deploy, or undeploy).
- UndeployPostScript
The type of the script.
Possible values: length = 7, Value must match regular expression
/^(ansible)$/
Examples:ansible
The path to this script is within the current version source.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^\\S+$/
Examples:scripts/validate-post-ansible-playbook.yaml
The short description for this script.
Possible values: 0 ≤ length ≤ 256, Value must match regular expression
/$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The state of the configuration.
Possible values: [
approved
,deleted
,deleting
,deleting_failed
,discarded
,draft
,deployed
,deploying_failed
,deploying
,superseded
,undeploying
,undeploying_failed
,validated
,validating
,validating_failed
,applied
,apply_failed
]The flag that indicates whether a configuration update is available.
The stack definition identifier.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The stack config parent of which this configuration is a member of.
- MemberOf
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The definition summary of the stack configuration.
- Definition
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The member deployabe architectures that are included in your stack.
Possible values: 0 ≤ number of items ≤ 100
- Members
The name matching the alias in the stack definition.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The version of the stack configuration.
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
A URL.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
/^(http(s)?:\/\/)[a-zA-Z0-9\\$\\-_\\.+!\\*'\\(\\),=&?\/]+$/
The configuration type.
Possible values: [
project_deployed
,user_deployed
,stack
]Computed state code clarifying the prerequisites for validation for the configuration.
Possible values: [
awaiting_input
,awaiting_prerequisite
,awaiting_validation
,awaiting_member_deployment
,awaiting_stack_setup
]The description of a project configuration.
- Definition
The profile that is required for compliance.
Examples:{ "attachment_id": "someattachmentid", "profile_name": "SCCProfilev1.0" }
- ComplianceProfile
The unique ID for the compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
A unique ID for the instance of a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The location of the compliance instance.
Possible values: [
us-south
,us-east
,eu-gb
,eu-de
,ca-tor
]A unique ID for the attachment to a compliance profile.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\/:a-zA-Z0-9\\.\\-]+$/
The name of the compliance profile.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
A unique concatenation of the catalog ID and the version ID that identify the deployable architecture in the catalog. I you're importing from an existing Schematics workspace that is not backed by cart, a
locator_id
is required. If you're using a Schematics workspace that is backed by cart, alocator_id
is not necessary because the Schematics workspace has one.There are 3 scenarios:
- If only a
locator_id
is specified, a new Schematics workspace is instantiated with thatlocator_id
. - If only a schematics
workspace_crn
is specified, a400
is returned if alocator_id
is not found in the existing schematics workspace. - If both a Schematics
workspace_crn
and alocator_id
are specified, a400
message is returned if the specifiedlocator_id
does not agree with thelocator_id
in the existing Schematics workspace. For more information of creating a Schematics workspace, see Creating workspaces and importing your Terraform template.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[\\.0-9a-z-A-Z_-]+$/
- If only a
A project configuration description.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
/^$|^(?!\\s)(?!.*\\s$)[^\\x00-\\x1F]*$/
The configuration name. It's unique within the account across projects and regions.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
/^[a-zA-Z0-9][a-zA-Z0-9-_ ]*$/
The ID of the project environment.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The authorization details. You can authorize by using a trusted profile or an API key in Secrets Manager.
Examples:{ "method": "trusted_profile", "trusted_profile_id": "Profile-9ac10c5c-195c-41ef-b465-68a6b6dg5f12" }
- Authorizations
The trusted profile ID.
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The authorization method. You can authorize by using a trusted profile or an API key in Secrets Manager.
Possible values: [
api_key
,trusted_profile
]The IBM Cloud API Key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
/^(?!\\s)(?!.*\\s$)[^`<>\\x00-\\x1F]*$/
The input variables that are used for configuration definition and environment.
The Schematics environment variables to use to deploy the configuration. Settings are only available if they are specified when the configuration is initially created.
Status Code
You successfully retrieved the version.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The example response to a request for a deployable architecture configuration draft.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "env-stage", "description": "The stage environment configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "ref:/configs/account-stage/inputs/account_id", "resource_group": "stage", "access_tags": [ "env:stage" ], "logdna_name": "The name of the LogDNA stage service instance.", "sysdig_name": "The name of the SysDig stage service instance." } }, "is_draft": true, "version": 2, "outputs": [ { "name": "resource_group_id" }, { "name": "logdna_id" }, { "name": "sysdig_id" } ], "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "schematics": { "workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139" }, "state": "validated", "update_available": true, "needs_attention_state": [], "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/b0c44146-1ef6-40c2-82ba-74d51149770a", "deployment_mode": "project_deployed" }
The example response to a request for a deployable architecture configuration draft.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "env-stage", "description": "The stage environment configuration.", "locator_id": "1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.018edf04-e772-4ca2-9785-03e8e03bef72-global", "inputs": { "account_id": "ref:/configs/account-stage/inputs/account_id", "resource_group": "stage", "access_tags": [ "env:stage" ], "logdna_name": "The name of the LogDNA stage service instance.", "sysdig_name": "The name of the SysDig stage service instance." } }, "is_draft": true, "version": 2, "outputs": [ { "name": "resource_group_id" }, { "name": "logdna_id" }, { "name": "sysdig_id" } ], "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "schematics": { "workspace_crn": "crn:v1:staging:public:schematics:us-south:a/38acaf4469814090a4e675dc0c317a0d:95ad49de-ab96-4e7d-a08c-45c38aa448e6:workspace:us-south.workspace.service.e0106139" }, "state": "validated", "update_available": true, "needs_attention_state": [], "created_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/b0c44146-1ef6-40c2-82ba-74d51149770a", "deployment_mode": "project_deployed" }
The example response to a request for a resource configuration draft.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "shared-resources-dev", "description": "The shared resources for dev environments.", "labels": [ "dev" ], "type": "manual", "resource_crns": [ "crn:v1:staging:public:toolchain:us-south:a/d11256044e024d5bbea1a7d7ee4575c3:618c70c7-0ead-40fb-86ce-e3f7b10c9f99::" ] }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "is_draft": false, "version": 2, "state": "applied", "needs_attention_state": [], "outputs": [], "created_at": "2023-02-22T19:51:23.253Z", "updated_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/293c3c36-a094-4115-a12b-de0a9ca39be5", "deployment_mode": "user_deployed" }
The example response to a request for a resource configuration draft.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5", "definition": { "name": "shared-resources-dev", "description": "The shared resources for dev environments.", "labels": [ "dev" ], "type": "manual", "resource_crns": [ "crn:v1:staging:public:toolchain:us-south:a/d11256044e024d5bbea1a7d7ee4575c3:618c70c7-0ead-40fb-86ce-e3f7b10c9f99::" ] }, "project": { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "definition": { "name": "iaas-infra-prestage-env" }, "crn": "crn:v1:staging:public:project:us-south:a/06580c923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a" }, "is_draft": false, "version": 2, "state": "applied", "needs_attention_state": [], "outputs": [], "created_at": "2023-02-22T19:51:23.253Z", "updated_at": "2023-02-22T19:51:23.253Z", "modified_at": "2023-02-22T19:51:23.253Z", "href": "https://projects.api.cloud.ibm.com/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a/configs/293c3c36-a094-4115-a12b-de0a9ca39be5", "deployment_mode": "user_deployed" }
Delete a project configuration version
Delete a configuration version by specifying the project ID.
Delete a configuration version by specifying the project ID.
Delete a configuration version by specifying the project ID.
Delete a configuration version by specifying the project ID.
DELETE /v1/projects/{project_id}/configs/{id}/versions/{version}
delete_config_version(
self,
project_id: str,
id: str,
version: int,
**kwargs,
) -> DetailedResponse
deleteConfigVersion(params)
(project *ProjectV1) DeleteConfigVersion(deleteConfigVersionOptions *DeleteConfigVersionOptions) (result *ProjectConfigDelete, response *core.DetailedResponse, err error)
(project *ProjectV1) DeleteConfigVersionWithContext(ctx context.Context, deleteConfigVersionOptions *DeleteConfigVersionOptions) (result *ProjectConfigDelete, response *core.DetailedResponse, err error)
Authentication
Request
Instantiate the DeleteConfigVersionOptions
struct and set the fields to provide parameter values for the DeleteConfigVersion
method.
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The configuration version.
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The configuration version.
parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The configuration version.
WithContext method only
A context.Context instance that you can use to specify a timeout for the operation or to cancel an in-flight request.
The DeleteConfigVersion options.
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The configuration version.
curl -X DELETE --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" "{base_url}/v1/projects/{project_id}/configs/{id}/versions/{version}"
deleteConfigVersionOptions := projectService.NewDeleteConfigVersionOptions( projectIdLink, configIdLink, int64(38), ) projectConfigDelete, response, err := projectService.DeleteConfigVersion(deleteConfigVersionOptions) if err != nil { panic(err) } b, _ := json.MarshalIndent(projectConfigDelete, "", " ") fmt.Println(string(b))
const params = { projectId: projectIdLink, id: configIdLink, version: 38, }; let res; try { res = await projectService.deleteConfigVersion(params); console.log(JSON.stringify(res.result, null, 2)); } catch (err) { console.warn(err); }
response = project_service.delete_config_version( project_id=project_id_link, id=config_id_link, version=38, ) project_config_delete = response.get_result() print(json.dumps(project_config_delete, indent=2))
Response
The ID of the deleted configuration.
The ID of the deleted project or configuration.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The ID of the deleted configuration.
The ID of the deleted project or configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The ID of the deleted configuration.
The ID of the deleted project or configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
The ID of the deleted configuration.
The ID of the deleted project or configuration.
Possible values: length ≤ 128, Value must match regular expression
/^[\\.\\-0-9a-zA-Z]+$/
Status Code
You successfully deleted the configuration version.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The supplied authentication is not authorized to view this resource.
The example response to a request to delete a configuration.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5" }
The example response to a request to delete a configuration.
{ "id": "293c3c36-a094-4115-a12b-de0a9ca39be5" }
Get the latest validation details
Retrieve the most recent validation details, which include job summary and logs.
GET /v1/projects/{project_id}/configs/{id}/versions/{version}/last_validated
Authentication
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The configuration version.
Response
The log from the last action job that is performed on the project configuration.
The cost estimate of the configuration. This property exists only after the first configuration validation.
The Code Risk Analyzer logs of the configuration. This property is populated only after the validation step when the Code Risk Analyzer is run. Note:
cra
is the abbreviated form of Code Risk Analyzer.A summary of an action with the logs.
A summary of an action with the logs.
A summary of an action with the logs.
The result of the last action.
Possible values: [
failed
,passed
]
Status Code
You successfully retrieved the details.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
Your request encountered a system problem or unexpected error.
The sample response for retrieving the job log of a project action.
{ "cost_estimate": {}, "cra_logs": {}, "job": { "id": "345b03e7440fce352ffc652050c34dbf", "log": "2023/06/08 04:38:29 --- Ready to execute the command ---", "summary": { "version": "1.0.5", "plan_summary": {}, "apply_summary": {}, "destroy_summary": {}, "message_summary": {}, "plan_messages": {}, "apply_messages": {}, "destroy_messages": {} } }, "result": "passed" }
Get the latest deployment details
Retrieve the latest deployment details, which include job summary and logs.
GET /v1/projects/{project_id}/configs/{id}/versions/{version}/last_deployed
Authentication
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The configuration version.
Response
The log from the last action job that is performed on the project configuration.
A summary of an action with the logs.
A summary of an action with the logs.
A summary of an action with the logs.
The result of the last action.
Possible values: [
failed
,passed
]
Status Code
You successfully retrieved the deployment details.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
Your request encountered a system problem or unexpected error.
The sample response for retrieving the job log of a project action.
{ "job": { "id": "345b03e7440fce352ffc652050c34dbf", "log": "2023/06/08 04:38:29 --- Ready to execute the command ---", "summary": { "version": "1.0.5", "plan_summary": {}, "apply_summary": {}, "destroy_summary": {}, "message_summary": {}, "plan_messages": {}, "apply_messages": {}, "destroy_messages": {} } }, "result": "passed" }
Get the latest undeployment action details
Retrieve the latest undeployment action details, including job summary and logs.
GET /v1/projects/{project_id}/configs/{id}/versions/{version}/last_undeployed
Authentication
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The configuration version.
Response
The log from the last action job that is performed on the project configuration.
A summary of an action with the logs.
A summary of an action with the logs.
A summary of an action with the logs.
The result of the last action.
Possible values: [
failed
,passed
]
Status Code
You successfully retrieved the undeployment action details.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
Your request encountered a system problem or unexpected error.
The sample response for retrieving the job log of a project action.
{ "job": { "id": "345b03e7440fce352ffc652050c34dbf", "log": "2023/06/08 04:38:29 --- Ready to execute the command ---", "summary": { "version": "1.0.5", "plan_summary": {}, "apply_summary": {}, "destroy_summary": {}, "message_summary": {}, "plan_messages": {}, "apply_messages": {}, "destroy_messages": {} } }, "result": "passed" }
Get the latest monitoring action details
Retrieve the latest monitoring action details, including job summary and logs.
GET /v1/projects/{project_id}/configs/{id}/versions/{version}/last_monitoring
Authentication
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The configuration version.
Response
The log from the last monitoring action job that is performed on the project configuration.
The log of drift detection jobs that were performed as part of the last monitoring action.
The result of the last action.
Possible values: [
failed
,passed
]
Status Code
You successfully retrieved the monitoring action details.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
Your request encountered a system problem or unexpected error.
The sample response for retrieving the job log of a monitoring action.
{ "drift_detection": { "job": { "id": "345b03e7440fce352ffc652050c34dbf", "log": "2023/06/08 04:38:29 --- Ready to execute the command ---", "summary": { "version": "1.0.5", "plan_summary": {}, "apply_summary": {}, "destroy_summary": {}, "message_summary": {}, "plan_messages": {}, "apply_messages": {}, "destroy_messages": {} } } }, "result": "passed" }
View the latest Schematics job
Retrieve the latest Schematics job that corresponds to a plan, deploy, or undeploy configuration resource action.
GET /v1/projects/{project_id}/configs/{id}/job/{action}
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The triggered action.
Allowable values: [
plan
,install
,uninstall
,validate
,deploy
,undeploy
]
Query Parameters
The timestamp of when the action was triggered.
Response
The response of a request to fetch an action job.
The unique ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Status Code
You successfully retrieved the job.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The request was not completed by the server. It could be due to an internal error or in some cases, invalid data in the request.
Your request encountered a system problem or unexpected error.
The sample response for retrieving the job of a project action.
{ "id": "345b03e7440fce352ffc652050c34dbf" }
Get the latest cost estimate from Schematics
Retrieve the most recent cost estimate from the Schematics cart order that is associated to a project configuration.
GET /v1/projects/{project_id}/configs/{id}/cost_estimate
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Response
The cost estimate for the specified configuration.
Status Code
You successfully retrieved the cost estimate.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
Your request encountered a system problem or an unexpected error.
{ "version": "0.2", "currency": "USD", "projects": [ { "name": "tfplan.json", "metadata": { "path": "tfplan.json", "infracostCommand": "breakdown", "type": "terraform_plan_json", "branch": "", "commit": "", "commitAuthorName": "", "commitAuthorEmail": "", "commitTimestamp": "1901-01-01T00:00:00.000Z", "commitMessage": "" }, "pastBreakdown": { "resources": [], "totalHourlyCost": "0", "totalMonthlyCost": "0" }, "breakdown": { "resources": [], "totalHourlyCost": "0", "totalMonthlyCost": "0" }, "diff": { "resources": [], "totalHourlyCost": "0", "totalMonthlyCost": "0" }, "summary": { "totalDetectedResources": 16, "totalSupportedResources": 0, "totalUnsupportedResources": 15, "totalUsageBasedResources": 0, "totalNoPriceResources": 1, "unsupportedResourceCounts": { "ibm_cd_tekton_pipeline": 1, "ibm_cd_tekton_pipeline_definition": 1, "ibm_cd_tekton_pipeline_property": 6, "ibm_cd_tekton_pipeline_trigger": 1, "ibm_cd_toolchain": 1, "ibm_cd_toolchain_tool_githubintegrated": 1, "ibm_cd_toolchain_tool_hostedgit": 1, "ibm_cd_toolchain_tool_pipeline": 1, "ibm_cos_bucket": 1, "ibm_resource_instance": 1 }, "noPriceResourceCounts": { "ibm_iam_access_group_policy": 1 } } } ], "totalHourlyCost": "0", "totalMonthlyCost": "0", "pastTotalHourlyCost": "0", "pastTotalMonthlyCost": "0", "diffTotalHourlyCost": "0", "diffTotalMonthlyCost": "0", "timeGenerated": "2022-08-12T15:43:53.277Z", "summary": { "totalDetectedResources": 16, "totalSupportedResources": 0, "totalUnsupportedResources": 15, "totalUsageBasedResources": 0, "totalNoPriceResources": 1, "unsupportedResourceCounts": { "ibm_cd_tekton_pipeline": 1, "ibm_cd_tekton_pipeline_definition": 1, "ibm_cd_tekton_pipeline_property": 6, "ibm_cd_tekton_pipeline_trigger": 1, "ibm_cd_toolchain": 1, "ibm_cd_toolchain_tool_githubintegrated": 1, "ibm_cd_toolchain_tool_hostedgit": 1, "ibm_cd_toolchain_tool_pipeline": 1, "ibm_cos_bucket": 1, "ibm_resource_instance": 1 }, "noPriceResourceCounts": { "ibm_iam_access_group_policy": 1 } } }
Retrieve Schematics Workspace State File
Retrieves the Schematics workspace state file.
GET /v1/projects/{project_id}/configs/{id}/retrieve_schematics_statefile
Authentication
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Response
The Schematics Terraform State File.
Status Code
You successfully retrieve the workspace state file.
The credentials are invalid or authentication is required to succeed.
The requested resource could not be found.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
Your request encountered a system problem or an unexpected error.
An example response of a Schematics Terraform State File
{ "version": 4, "terraform_version": "1.2.6", "serial": 2, "lineage": "e57cace8-5713-2039-d438-33ba6b8ac4e4", "outputs": { "boolean_output": { "value": true, "type": "bool" } }, "resources": [] }
Execute Schematics Workspace State Commands
Executes the Schematics workspace state commands.
POST /v1/projects/{project_id}/configs/{id}/execute_schematics_commands
Authentication
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
A batch of one or more references.
An example request payload for executing Schematics Commands.
{
"commands": [
{
"command": "taint",
"command_params": "null_resource.sleep",
"command_name": "Test1",
"command_desc": "Making taint",
"command_onerror": "continue"
}
]
}
An array to store the commands.
Possible values: 1 ≤ number of items ≤ 50
Response
The Schematics Terraform Result.
Status Code
You successfully updated the workspace metadata.
The request body is either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The requested resource could not be found.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
Your request encountered a system problem or an unexpected error.
An example request payload for executing Schematics Commands.
{ "activityid": "5958288bbfce4fde8491cdb20568f3e9" }
Create a project CRN token
Refresh a project CRN token by creating a new one.
POST /v1/projects/{id}/token
Authentication
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Response
The project CRN token
The IAM access token.
The number of seconds that were counted since 1 January 1970 until the IAM access token expires.
Status Code
You successfully created a project CRN token.
The credentials are invalid or authentication is required to succeed.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
A project or project configuration CRN token
{ "access_token": "ACCESS_TOKEN", "expiration": 1616750582 }
Create a project configuration CRN token
Refresh a project configuration CRN token by creating a new one.
POST /v1/projects/{project_id}/configs/{id}/token
Authentication
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Response
The project configuration CRN token
The IAM access token.
The number of seconds that were counted since 1 January 1970 until the IAM access token expires.
Status Code
You successfully created a project configuration CRN token.
The credentials are invalid or authentication is required to succeed.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
A project or project configuration CRN token
{ "access_token": "ACCESS_TOKEN", "expiration": 1616750582 }
Add notifications
Create a notification event to be stored in the project definition.
POST /v1/projects/{id}/event
Authentication
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
A valid notification event that follows the Event Notifications schema.
A post notifications request example.
{
"notifications": [
{
"event": "project.create.failed",
"target": "234234324-3444-4556-224232432",
"source": "id.of.project.service.instance",
"triggered_by": "user-iam-id",
"action_url": "actionable/url",
"data": {
"field1": 1
}
}
]
}
A collection of the notification events to post.
Possible values: 1 ≤ number of items ≤ 10000
Response
The response of a notification post.
A collection of the notification events with status.
Possible values: 1 ≤ number of items ≤ 10000
Status Code
You successfully posted a notification.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
A post notifications response example.
{ "_id": "9n121be-3b7d-4bad-9bdd-2b0d7b3dcb6d", "event": "project.create.failed", "target": "234234324-3444-4556-224232432", "source": "id.of.project.service.instance", "triggered_by": "user-iam-id", "data": { "field1": 1 }, "status": "SUCCESS" }
List all notifications events
Retrieve all the notification events by specifying the project ID.
GET /v1/projects/{id}/event
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Response
The response from a request to fetch notifications.
A collection of the notification events with an ID.
Possible values: 0 ≤ number of items ≤ 10000
Status Code
You successfully retrieved the notification events.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
Your request encountered a system problem or unexpected error.
A response example a get notifications request.
{ "notifications": [ { "id": "9n121be-3b7d-4bad-9bdd-2b0d7b3dcb6d", "event": "project.create.failed", "target": "234234324-3444-4556-224232432", "source": "id.of.project.service.instance", "triggered_by": "user-iam-id" }, { "id": "234234324-3444-4556-224232432", "event": "check.pipeline.failed", "target": "pull.request.id", "source": "pipeline.id", "target_label": "config_name2" } ] }
Send a webhook for catalog events
Send a webhook for pulsar catalog events.
POST /v1/pulsar/catalog_events
Authentication
Request
A pulsar catalog event.
A pulsar event request example.
[
{
"event_type": "account.create",
"timestamp": "2017-10-10T01:22:38.665Z",
"publisher": "bluemix.account.management",
"account_id": "7e1dbfafb670594f3e95a2fa9b1aa9a8",
"version": "1.0",
"event_id": "5f208fef-6b64-413c-aa07-dfed0b46abc1236",
"event_properties": {
"user_id": "IBMid-xaab1235nn",
"account.plan": "TRIAL",
"account.state": "INACTIVE"
}
}
]
The type of the event that is published and written in dot notation.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
^\S+$
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The publisher of the events, preferably written as the service's CRN.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
^\S+$
The IBMid that the event is scoped to.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
^\S+$
The version of the payload.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
^\S+$
The custom event properties for a specific event.
A unique identifier for that individual event.
Possible values: 1 ≤ length ≤ 300, Value must match regular expression
^\S+$
Response
Status Code
The pulsar event webhook that you sent was accepted.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
No Sample Response
Send a webhook for Event Notifications events
Send a webhook for events in an Event Notifications instance.
POST /v1/pulsar/event_notification_events
Authentication
Request
The request body of webhook for a pulsar event.
A pulsar event request example.
[
{
"event_type": "account.create",
"timestamp": "2017-10-10T01:22:38.665Z",
"publisher": "bluemix.account.management",
"account_id": "7e1dbfafb670594f3e95a2fa9b1aa9a8",
"version": "1.0",
"event_id": "5f208fef-6b64-413c-aa07-dfed0b46abc1236",
"event_properties": {
"user_id": "IBMid-xaab1235nn",
"account.plan": "TRIAL",
"account.state": "INACTIVE"
}
}
]
The type of the event that is published and written in dot notation.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
^\S+$
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The publisher of the events, preferably written as the service's CRN.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
^\S+$
The IBMid that the event is scoped to.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
^\S+$
The version of the payload.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
^\S+$
The custom event properties for a specific event.
A unique identifier for that individual event.
Possible values: 1 ≤ length ≤ 300, Value must match regular expression
^\S+$
Response
Status Code
Your pulsar event webhook was accepted.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
No Sample Response
Request
Query Parameters
Set this parameter if you want to get the dependencies status in the output response.
Default:
true
Response
The response data from a health check request.
The name of the service.
The running version of the service.
The status of service dependencies.
- dependencies
Status Code
You successfully retrieved the health information.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
{ "name": "projects", "version": "0.0.1", "dependencies": { "database": 0, "hypersync": 1 } }
Create a service instance
Create a service instance. When the service broker receives a provision request from the IBM Cloud platform, the broker must take whatever action is necessary to create a new resource. When a user creates a service instance from the IBM Cloud console or the IBM Cloud CLI, the IBM Cloud platform validates that the user has permission to create the service instance by using IBM Cloud IAM. After this validation occurs, your service broker's provision endpoint (PUT /v2/resource_instances/:instance_id) starts. When provisioning occurs, the IBM Cloud platform provides the following values:
- The IBM Cloud context is included in the context variable. - The X-Broker-API-Originating-Identity has the IBM IAM ID of the user that initiated the request. - The parameters section includes the requested location and additional parameters that are required by your service.
PUT /v2/service_instances/{instance_id}
Authentication
Request
Custom Headers
The broker API version.
Possible values: 1 ≤ length ≤ 100, Value must match regular expression
^(\d+\.)?(\d+\.)?(\*|\d+)$
Example:
1.0
The broker API originating identity.
Possible values: 0 ≤ length ≤ 300, Value must match regular expression
^$|^(?!\s).*\S$
Example:
ibmcloud eyJpYW1fbWQiOiJJQk2pZC03MEdOUjcxN2lFIn0=
Path Parameters
The instance ID of a service instance that is provided by the IBM Cloud platform.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
(?!\s)(?!.*\s$)^(crn)[^'"`<>{}\s\x00-\x1F]*
Example:
crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
Query Parameters
A value of
true
indicates that both the IBM Cloud platform and the requesting client support asynchronous deprovisioning. If this parameter is not included in the request, and the broker can deprovision only a service instance of the requested plan asynchronously, the broker must reject the request with a 422 Unprocessable Entity response code.Default:
true
The request body, which contains the query filters and the search token that is initially set. null or undefined.
The ID of the service that is stored in the
catalog.j-son
of your broker. This value must be a GUID or a nonempty string.Possible values: 1 ≤ length ≤ 128, Value must match regular expression
^\S+$
The ID of the plan for the requested service instance. This value is stored in the
catalog.j-son
of your broker.Possible values: 1 ≤ length ≤ 128, Value must match regular expression
^\S+$
The platform-specific contextual information where the service instance is provisioned.
The configuration options for the service instance. Aa an opaque object, the controller treats this value as a blob. Brokers must ensure that the client provided valid configuration parameters and values for the operation. If this field is not present in the request message, then the broker must not change the parameters of the instance as a result of this request.
The information about the service instance before the update.
Response
The result of the provision call.
The URL of a web-based management user interface for the service instance. The URL must contain enough information for the dashboard to identify the resource that is being accessed.
For asynchronous responses, service brokers can return an identifier that represents the operation. The value of this field must be provided by the platform with requests to the
last_operation
endpoint in a URL encoded query parameter. If present, this property must be a nonempty string.
Status Code
You successfully created a service instance.
The new resource was created.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The request cannot be processed because of a conflict between the request and the current client-controlled state in the system.
An example response to a provision call.
{ "dashboard_url": "/v1/projects/cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "operation": "replace_service_instance" }
An example error from provisioning or deprovisioning.
{ "errors": [ { "code": "provision_call_error", "message": "Error from provision call" } ], "trace": "6ba7b810-9dad-11d1-80b4-00c04fd430c8", "status_code": 201 }
Delete a project service instance
Delete or deprovision a project service instance by specifying the instance ID. When a service broker receives a delete request from the IBM Cloud platform, the broker must delete any resources that it created during the provision. Usually this action means that all resources are immediately reclaimed for future provisions.
DELETE /v2/service_instances/{instance_id}
Authentication
Request
Custom Headers
The broker API version.
Possible values: 1 ≤ length ≤ 100, Value must match regular expression
^(\d+\.)?(\d+\.)?(\*|\d+)$
Example:
1.0
The broker API originating identity.
Possible values: 0 ≤ length ≤ 300, Value must match regular expression
^$|^(?!\s).*\S$
Example:
ibmcloud eyJpYW1fbWQiOiJJQk2pZC03MEdOUjcxN2lFIn0=
Path Parameters
The ID of a previously provisioned service instance.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
(?!\s)(?!.*\s$)^(crn)[^'"`<>{}\s\x00-\x1F]*
Example:
crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
Query Parameters
The ID of the plan for which the service instance was requested. The plan ID is stored in the catalog.json of your broker. This value should be a GUID. It must be a nonempty string.
Possible values: 0 ≤ length ≤ 300, Value must match regular expression
^$|^(?!\s).*\S$
Example:
cb54391b-3316-4943-a5a6-a541678c1924
The ID of the service that is stored in the catalog.json of your broker. This value must be a GUID and a nonempty string.
Possible values: 0 ≤ length ≤ 300, Value must match regular expression
^$|^(?!\s).*\S$
Example:
cb54391b-3316-4943-a5a6-a541678c1924
A value of
true
indicates that both the IBM Cloud platform and the requesting client support asynchronous deprovisioning. If this parameter is not included in the request, and the broker can deprovision only a service instance of the requested plan asynchronously, the broker must reject the request with a 422 Unprocessable Entity response code. Learn more.Default:
false
Response
The result of deprovisioning a service instance.
Status Code
You successfully deleted a project service instance.
Your request was accepted.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request. This response code is returned if the broker supports only asynchronous provisioning for the requested plan and the request did not include
?accepts_incomplete=true
.The requested resource is no longer available.
An example response to a request to deprovision a service instance.
{}
An example error from provisioning or deprovisioning.
{ "errors": [ { "code": "provision_call_error", "message": "Error from provision call" } ], "trace": "6ba7b810-9dad-11d1-80b4-00c04fd430c8", "status_code": 201 }
Update plans and service parameters
Update the plans and service parameters in a provisioned service instance.
PATCH /v2/service_instances/{instance_id}
Authentication
Request
Custom Headers
The broker API version.
Possible values: 1 ≤ length ≤ 100, Value must match regular expression
^(\d+\.)?(\d+\.)?(\*|\d+)$
Example:
1.0
The originating identity of the broker API.
Possible values: 0 ≤ length ≤ 300, Value must match regular expression
^$|^(?!\s).*\S$
Example:
ibmcloud eyJpYW1fbWQiOiJJQk2pZC03MEdOUjcxN2lFIn0=
Path Parameters
The ID of a service instance that was previously provisioned.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
(?!\s)(?!.*\s$)^(crn)[^'"`<>{}\s\x00-\x1F]*
Example:
crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
Query Parameters
A value of
true
indicates that both the IBM Cloud platform and the requesting client support asynchronous deprovisioning. If this parameter is not included in the request, and the broker can deprovision only a service instance of the requested plan asynchronously, the broker must reject the request with a 422 Unprocessable Entity response code.Default:
false
The request body that contains the query filters and the search token that is initially set. This field is null or undefined.
{
"context": {
"account_id": "499b176abb3e1c9727df87ae48b27c7b",
"crn": "crn:v1:bluemix:public:testjavaresourceservicebrokername:us-south:a/499b176abb3e1c9727df87ae48b27c7b:7f0d2b93-fd4a-4ce9-8675-978d20b1e0b7::",
"platform": "ibmcloud",
"resource_group_crn": "crn:v1:bluemix:public:resource-controller::a/499b176abb3e1c9727df87ae48b27c7b::resource-group:2a5f74056b254efbaab5e9e28a7111414",
"target_crn": "crn:v1:bluemix:public:resource-catalog::a/e97a8c01ac694e308ef3ad7795c7cdb3::deployment:e62e2c19-0c3b-41e3-b8b3-c71762ecd489%3Aus-south38399"
},
"parameters": {
"parameter1": 1,
"parameter2": "value"
},
"plan_id": "e1031579-4b42-4169-b7cf-f7793c616fdc",
"previous_values": {
"plan_id": "e62e2c19-0c3b-41e3-b8b3-c71762ecd489",
"service_id": "cb55391b-3416-4943-a6a6-a541778c1924"
},
"service_id": "cb55391b-3416-4943-a6a6-a541778c1924"
}
The ID of the service that is stored in the
catalog.j-son
of your broker. This value must be a GUID or a nonempty string.Possible values: 1 ≤ length ≤ 128, Value must match regular expression
^\S+$
The platform-specific contextual information where the service instance is provisioned.
The configuration options for the service instance. As an opaque object, the controller treats this property as a blob. Brokers must ensure that the client provided valid configuration parameters and values for the operation. If this field is not present in the request message, then the broker must not change the parameters of the instance as a result of this request.
The ID of the plan for the requested service instance., This value is stored in the
catalog.j-son
of your broker.Possible values: 1 ≤ length ≤ 128, Value must match regular expression
^\S+$
The information about the service instance before the update.
Response
The result of updating a service instance.
Status Code
You successfully updated the parameters.
The new resource was created.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
An example response to a request to update a service instance.
{}
An example error from provisioning or deprovisioning.
{ "errors": [ { "code": "provision_call_error", "message": "Error from provision call" } ], "trace": "6ba7b810-9dad-11d1-80b4-00c04fd430c8", "status_code": 201 }
Get the last operation for an instance
Retrieve the previous operations for a service instance by specifying the instance ID for asynchronous provision calls.
GET /v2/service_instances/{instance_id}/last_operation
Authentication
Request
Custom Headers
The broker API version.
Possible values: 1 ≤ length ≤ 100, Value must match regular expression
^(\d+\.)?(\d+\.)?(\*|\d+)$
Example:
1.0
Path Parameters
The unique instance ID that the IBM Cloud platform generates during provisioning.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
(?!\s)(?!.*\s$)^(crn)[^'"`<>{}\s\x00-\x1F]*
Example:
crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
Query Parameters
A broker-provided identifier for the operation.
Possible values: 0 ≤ length ≤ 50, Value must match regular expression
^$|^(?!\s).*\S$
Example:
ABCD
The ID of the plan from the catalog.json in your broker.
Possible values: 0 ≤ length ≤ 300, Value must match regular expression
^$|^(?!\s).*\S$
Example:
cb54391b-3316-4943-a5a6-a541678c1924
The ID of the service from the catalog.json in your service broker.
Possible values: 0 ≤ length ≤ 300, Value must match regular expression
^$|^(?!\s).*\S$
Example:
cb54391b-3316-4943-a5a6-a541678c1924
Response
The result of get_last_operation
call.
The valid values are in progress, succeeded, and failed.
A user-facing message that is displayed to the platform API client. This property can be used to tell the user details about the status of the operation.
Status Code
You successfully retrieved the previous operations for an instance.
The requested resource is no longer available.
An example response to a request to get the last operation.
{ "state": "succeeded", "description": "The last operation was retrieved successfully." }
Update the state of a service instance
Update an instance by disabling or enabling the state of a provisioned service instance.
PUT /bluemix_v1/service_instances/{instance_id}
Authentication
Request
Custom Headers
The broker API version.
Possible values: 1 ≤ length ≤ 100, Value must match regular expression
^(\d+\.)?(\d+\.)?(\*|\d+)$
Example:
1.0
Path Parameters
The instance ID of a service instance that is provided by the IBM Cloud platform.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
(?!\s)(?!.*\s$)^(crn)[^'"`<>{}\s\x00-\x1F]*
Example:
crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
It contains the query filters and the search token that is initially set to null or undefined.
{
"enabled": true
}
The ID of the service that is stored in the
catalog.j-son
of your broker. This value must be a GUIID or a nonempty string.This property is an optional string that shows the user ID that is initiating the call.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
^\S+$
This property is an optional string that states the reason code for the service instance state change. Valid values are
IBMCLOUD_ACCT_ACTIVATE
,IBMCLOUD_RECLAMATION_RESTORE
, orIBMCLOUD_SERVICE_INSTANCE_BELOW_CAP
for enable calls. Or you can useIBMCLOUD_ACCT_SUSPEND
,IBMCLOUD_RECLAMATION_SCHEDULE
, orIBMCLOUD_SERVICE_INSTANCE_ABOVE_CAP
for disable calls. UseIBMCLOUD_ADMIN_REQUEST
for enable and disable calls.The ID of the plan for the requested service instance. This value is stored in the
catalog.j-son
of your broker.Possible values: 1 ≤ length ≤ 128, Value must match regular expression
^\S+$
The information about the service instance before the update.
Response
The result of the status call of a service instance.
This property indicates whether the service instance is active and is meaningful if enabled is set to
true
. The default value istrue
if it's not specified.This property indicates the current state of the service instance.
This property indicates when the service instance was last accessed or modified. It is meaningful if enabled is set to
true
and active is set tofalse
. This property is represented as milliseconds since the epoch, but does not need to be accurate to the second or hour.
Status Code
Your request was successful.
The state of the provisioned service instance was successfully updated.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
An example of a response to a request for the resource state.
{ "active": "false", "enabled": "true", "last_active": "1673273819000" }
An example error from provisioning or deprovisioning.
{ "errors": [ { "code": "provision_call_error", "message": "Error from provision call" } ], "trace": "6ba7b810-9dad-11d1-80b4-00c04fd430c8", "status_code": 201 }
Get the current state information
Retrieve the current state for the specified service instance.
GET /bluemix_v1/service_instances/{instance_id}
Authentication
Request
Custom Headers
The broker API version.
Possible values: 1 ≤ length ≤ 100, Value must match regular expression
^(\d+\.)?(\d+\.)?(\*|\d+)$
Example:
1.0
Path Parameters
The ID of a service instance that was previously provisioned.
Possible values: 4 ≤ length ≤ 512, Value must match regular expression
(?!\s)(?!.*\s$)^(crn)[^'"`<>{}\s\x00-\x1F]*
Example:
crn:v1:staging:public:project:us-south:a/4e1c48fcf8ac33c0a2441e4139f189ae:bf40ad13-b107-446a-8286-c6d576183bb1::
Response
The result of the status call of a service instance.
This property indicates whether the service instance is active and is meaningful if enabled is set to
true
. The default value istrue
if it's not specified.This property indicates the current state of the service instance.
This property indicates when the service instance was last accessed or modified. It is meaningful if enabled is set to
true
and active is set tofalse
. This property is represented as milliseconds since the epoch, but does not need to be accurate to the second or hour.
Status Code
The request was successful.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The requested resource could not be found.
An example of a response to a request for the resource state.
{ "active": "false", "enabled": "true", "last_active": "1673273819000" }
Get the catalog metadata
Fetch the catalog metadata that is stored within the broker.
GET /v2/catalog
Authentication
Request
Custom Headers
The broker API version.
Possible values: 1 ≤ length ≤ 100, Value must match regular expression
^(\d+\.)?(\d+\.)?(\*|\d+)$
Example:
1.0
Response
The response from a request to fetch the catalog metadata that is stored within the broker.
The collection of catalog services.
Possible values: 0 ≤ number of items ≤ 10000
Status Code
Your request was successful.
An example response to a request for catalog metadata.
{ "services": [ { "metadata": { "type": "public", "longDescription": "The project service is the platform service that manages Infrastructure as Code projects.", "serviceKeysSupported": false, "displayName": "Project", "featuredImageUrl": "https://broker.project.test.cloud.ibm.com/logo.svg", "documentationUrl": "https://www.ibm.com/docs/", "providerDisplayName": "IBM", "termsUrl": "https://www-03.ibm.com/software/sla/sladb.nsf/pdf/5948-09/$file/i126-5948-09_08-2020_en_US.pdf", "parameters": [], "imageUrl": "https://broker.project.test.cloud.ibm.com/logo.svg", "smallImageUrl": "https://broker.project.test.cloud.ibm.com/logo.svg", "mediumImageUrl": "https://broker.project.test.cloud.ibm.com/logo.svg", "supportUrl": "https://www.ibm.com/support", "supportEmail": "support@ibm.com", "instructionsUrl": "https://test.cloud.ibm.com/docs/get-coding/projects.html" }, "bindable": false, "rc_compatible": true, "iam_compatible": true, "plan_updateable": false, "unique_api_key": false, "tags": [ "rc_compatible", "ibm_created" ], "name": "project", "id": "5e3a7a60-ecb1-11ec-ba3d-5596cf8703a4", "description": "The project service.", "provisionable": false, "plans": [ { "name": "Free", "free": true, "description": "Free", "id": "aff3edfa-9baf-484a-a95e-4c9312b2b9b8", "metadata": { "regional": false, "allowInternalUsers": true, "displayName": "Free", "bullets": [ "Free plan" ] }, "pricingCatalogRev": "1-3df7625e4713a614ac0ab563026e8c6a", "pricingCatalogId": "f1f69175dce95ca9d958bb9b31828081", "effective_from": "2022-09-01T00:00:00.000Z", "effective_until": "9999-12-31T00:00:00.000Z" } ] } ] }
Connect to an Event Notifications instance
Connect a project instance to an Event Notifications instance.
POST /v1/projects/{id}/event_notifications
Authentication
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The metadata on the integration of the projects with Event Notifications.
A post integrations event notification request example.
{
"description": "A sample project source.",
"enabled": true,
"event_notifications_source_name": "project 1 source name for event notifications",
"instance_crn": "CRN of event notifications instance"
}
A CRN of the Event Notifications instance.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
^(?!\s).+\S$
A description of the Event Notifications instance.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
^$|^(?!\s).*\S$
The name of the project source for the Event Notifications instance.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
^(?!\s).+\S$
A status of the Event Notifications instance.
Response
The response of a request to connect a project to an Event Notifications instance.
The description of the Event Notifications instance.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
^$|^(?!\s).*\S$
The name of the Event Notifications instance.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
^(?!\s).+\S$
The status of the Event Notifications instance.
The unique ID of the Event Notifications instance.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
^(?!\s).+\S$
The type of the Event Notifications instance.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
^(?!\s).+\S$
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
Status Code
You successfully connected to an Event Notifications instance.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
A response example of a post integrations event notification request.
{ "description": "A sample project source.", "enabled": true, "id": "CRN of the project instance", "name": "Project name", "created_at": "2017-10-10T01:22:38.665Z" }
Get Event Notifications source details
Retrieve the source details of the project from the connected Event Notifications instance by specifying the project ID.
GET /v1/projects/{id}/event_notifications
Authentication
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Response
The response of a request to get the source details of the Event Notifications integration.
The description of the Event Notifications instance.
Possible values: 0 ≤ length ≤ 1024, Value must match regular expression
^$|^(?!\s).*\S$
The name of the Event Notifications instance.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
^(?!\s).+\S$
The status of the Event Notifications instance.
A unique ID of the Event Notifications instance.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
^(?!\s).+\S$
The type of the Event Notifications instance.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
^(?!\s).+\S$
A date and time value in the format YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ to match the date and time format as specified by RFC 3339.
Possible values: 20 ≤ length ≤ 64, Value must match regular expression
^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d+)?Z$
The topic count of the Event Notifications instance.
The topic names of the Event Notifications instance.
Possible values: 0 ≤ number of items ≤ 10000, 1 ≤ length ≤ 64, Value must match regular expression
^(?!\s).+\S$
Status Code
You successfully retrieved the source details.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
Your request encountered a system problem or unexpected error.
A response example of a request to get Event Notifications integrations.
{ "description": "A sample project source.", "enabled": true, "id": "CRN of the project instance.", "name": "Project name", "updated_at": "2017-10-10T01:22:38.665Z", "topic_count": 1, "topic_names": [ "topic 1" ] }
Delete an event notifications connection
Delete the Event Notifications integration if that is where the project was onboarded to.
DELETE /v1/projects/{id}/event_notifications
Authentication
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Response
Status Code
The request was successful but the response is empty.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
Your request encountered a system problem or unexpected error.
No Sample Response
Send a notification to Event Notifications
Send a notification to the Event Notifications instance by specifying the project ID.
POST /v1/projects/{id}/event_notifications/test
Authentication
Request
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The request body to post a notification to the Event Notifications API.
A post event notification request example.
{
"ibmendefaultlong": "long test notification message",
"ibmendefaultshort": "Test notification"
}
The IBM default long message for the Event Notifications instance.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
^(?!\s).+\S$
The IBM default short message for the Event Notifications instance.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
^(?!\s).+\S$
Response
The response for a request to post a test notification to the Event Notifications instance.
A unique ID of the Event Notifications instance.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
^(?!\s).+\S$
The source of the Event Notifications instance.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
^(?!\s).+\S$
The data content type of the Event Notifications instance.
Possible values: 1 ≤ length ≤ 128, Value must match regular expression
^(?!\s).+\S$
The IBM default long message for the Event Notifications instance.
Possible values: 1 ≤ length ≤ 1024, Value must match regular expression
^(?!\s).+\S$
The IBM default short message for the Event Notifications instance.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
^(?!\s).+\S$
The IBM source ID for the Event Notifications instance.
Possible values: 1 ≤ length ≤ 512, Value must match regular expression
^(?!\s).+\S$
The spec.version of the Event Notifications instance.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
^(?!\s).+\S$
The type of the Event Notifications instance.
Possible values: 1 ≤ length ≤ 64, Value must match regular expression
^(?!\s).+\S$
Status Code
You successfully posted the test notification to the Event Notifications instance.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
A post event notification response example.
{ "datacontenttype": "application/json", "ibmendefaultlong": "long test notification message", "ibmendefaultshort": "Test notification", "ibmensourceid": "crn of project", "id": "5f208fef-6b64-413c-aa07-dfed0b46abc1236", "notification_id": "234234324-3444-4556-224232432", "source": "crn of project", "specversion": "1.0", "type": "com.ibm.cloud.project.project.test_notification" }
List Security and Compliance Center instances for a project
Retrieve a list of Security and Compliance instances for a specific project by specifying the project ID. Learn more.
GET /v1/projects/{project_id}/compliance_instances
Authentication
Request
Custom Headers
The IBM trusted profile ID
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
^(?!\s)(?!.*\s$)[^`<>\x00-\x1F]*$
The IBM Cloud API key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
^(?!\s)(?!.*\s$)[^`<>\x00-\x1F]*$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique environment ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Response
The response to a request to fetch instances from Security and Compliance Center.
An array of Security and Compliance instances.
Possible values: 0 ≤ number of items ≤ 1000
Status Code
You successfully retrieved the list of instances.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
Your request encountered a system problem or unexpected error.
The example of a Security and Compliance Center instance result.
{ "compliance_instances": [ { "name": "compliance", "region": "us-south", "service_instance": "7c80d661-6629-47b0-a203-0469856f72aa", "crn": "crn:v1:staging:public:compliance:global:a/cfbf9050ab8eac97b01bab5af830be8a:7c80d661-6629-47b0-a203-0469856f72aa::" } ] }
List Security and Compliance Center profiles
Retrieve a list of Security and Compliance profiles in an instance for a specific project. Learn more.
GET /v1/projects/{project_id}/compliance_instances/{compliance_instance_id}/profiles
Authentication
Request
Custom Headers
The IBM trusted profile ID
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
^(?!\s)(?!.*\s$)[^`<>\x00-\x1F]*$
The IBM Cloud API key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
^(?!\s)(?!.*\s$)[^`<>\x00-\x1F]*$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique environment ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The ID of the Security and Compliance Center instance.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Query Parameters
The location of the Security and Compliance instance.
Possible values: 2 ≤ length ≤ 12, Value must match regular expression
^[a-z0-9-_]{2,}$
Example:
us-south
The last entry that is returned on the page. The server uses this parameter to determine the first entry that is returned on the next page. If this parameter is not specified, the logical first page is returned.
Possible values: 0 ≤ length ≤ 1536, Value must match regular expression
^$|^(?!\s)(?!.*\s$)[^\x00-\x1F]*$
Default:
The maximum number of resources to return. The number of resources that are returned is the same, except for the last page.
Possible values: 1 ≤ value ≤ 100
Default:
10
Response
The response to a request to fetch profiles from Security and Compliance Center.
An array of Security and Compliance profiles.
Possible values: 0 ≤ number of items ≤ 1000
Status Code
You successfully retrieved the list of profiles.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
Your request encountered a system problem or unexpected error.
The response example to a request for a Security and Compliance Center profile.
{ "limit": 10, "first": { "start": "start-here-for-this-page" }, "next": { "start": "start-here-for-next-page" }, "profiles": [ { "id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "profile_name": "IBM Cloud Security Best Practices", "profile_description": "The IBM Cloud Security Best Practices profile.", "profile_type": "predefined", "profile_version": "1.0.0" } ] }
List all Security and Compliance Center attachments
Retrieve a list of Security and Compliance Center profile attachments in an instance for a specific project. Learn more.
GET /v1/projects/{project_id}/compliance_instances/{compliance_instance_id}/profiles/{profile_id}/attachments
Authentication
Request
Custom Headers
The IBM trusted profile ID
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
^(?!\s)(?!.*\s$)[^`<>\x00-\x1F]*$
The IBM Cloud API key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
^(?!\s)(?!.*\s$)[^`<>\x00-\x1F]*$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique environment ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The ID of the Security and Compliance Center instance.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The ID of the Security and Compliance Center profile.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Query Parameters
The location of the Security and Compliance instance.
Possible values: 2 ≤ length ≤ 12, Value must match regular expression
^[a-z0-9-_]{2,}$
Example:
us-south
The last entry that is returned on the page. The server uses this parameter to determine the first entry that is returned on the next page. If this parameter is not specified, the logical first page is returned.
Possible values: 0 ≤ length ≤ 1536, Value must match regular expression
^$|^(?!\s)(?!.*\s$)[^\x00-\x1F]*$
Default:
The maximum number of resources to return. The number of resources that are returned is the same, except for the last page.
Possible values: 1 ≤ value ≤ 100
Default:
10
Response
The response to a request to fetch attachments for a specific profile from Security and Compliance Center.
An array of Security and Compliance profile attachments.
Possible values: 0 ≤ number of items ≤ 1000
Status Code
The request was successful.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
Your request encountered a system problem or unexpected error.
The example of a Security and Compliance Center attachment result.
{ "limit": 10, "first": { "start": "start-here-for-this-page" }, "next": { "start": "start-here-for-next-page" }, "profile_id": "cfbf9050-ab8e-ac97-b01b-ab5af830be8a", "attachments": [ { "id": "8ed89422c35043b2ac773cc40da97aa6", "included_scope": { "scope_id": "9ce219d8a13b4b46bd150929a40ad90d", "scope_type": "account" }, "attachment_parameters": [ { "parameter_name": "hpcs_crypto_units", "parameter_type": "string_list", "parameter_value": "['2', '3']", "assessment_type": "automated", "assessment_id": "rule-064d9004-8728-4988-b19a-1805710466f6" } ], "last_scan": "a96b9472-2b2d-4ac7-80d5-d93c52da08d1", "last_scan_status": "in_progress", "last_scan_time": "2023-04-17T14:30:14Z", "next_scan_time": "2023-04-17T20:30:14Z" } ] }
List all environments
Retrieve a list of all environments in your account across projects.
GET /v1/environments
Authentication
Response
The list environment response for IAM.
The environment.
Possible values: 0 ≤ number of items ≤ 10000
Status Code
You successfully retrieved a list of environments.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The sample environment list response for IAM.
{ "environments": [ { "value": "env123", "label": "development" } ] }
Add the configuration authorization token to the target endpoint
Inject the authorization token that is found or generated from the project configuration to allow users to call the target endpoint in the scope of the target account of the project configuration.
POST /v1/projects/{project_id}/configs/{id}/proxy_passthrough
Authentication
Request
Custom Headers
The IBM trusted profile ID
Possible values: 0 ≤ length ≤ 512, Value must match regular expression
^(?!\s)(?!.*\s$)[^`<>\x00-\x1F]*$
The IBM Cloud API key. It can be either raw or pulled from the catalog via a
CRN
orJSON
blob.Possible values: 0 ≤ length ≤ 512, Value must match regular expression
^(?!\s)(?!.*\s$)[^`<>\x00-\x1F]*$
The unique environment ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Path Parameters
The unique project ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
The unique configuration ID.
Possible values: length ≤ 128, Value must match regular expression
^[\.\-0-9a-zA-Z]+$
Query Parameters
The target endpoint that the project service is proxied through.
Possible values: 1 ≤ length ≤ 256, Value must match regular expression
^(http(s)?:\/\/)[a-zA-Z0-9\$\-_\.+!\*'\(\),=&?\/]+$
The payload to pass to the target endpoint.
{
"context": "foo"
}
Response
Status Code
You successfully added the token to the target endpoint.
The input parameters in the request body are either incomplete or in the wrong format. Be sure to include all the required parameters in your request.
The credentials are invalid or authentication is required to succeed.
The request could not be completed by the server. It could be due to an internal error or in some cases invalid data in the request.
Your request encountered a system problem or unexpected error.
{ "options": [] }