Skip to main content

UpdateBlueprintInstancePayload

changeSetIdstringrequired

The ID of the change set to use to deploy the blueprint instance update. When updating an existing blueprint instance (deploying), a change set is used instead of the deployment process re-computing the changes that need to be applied.

The source blueprint document is still required in addition to a change set to finish of resolving substitutions that can only be resolved at deploy time and for deployment orchestration. The source blueprint document is not used to compute changes at the deployment stage.

Example: a471bbb8-1267-4e65-873b-fa86bca71fcf
fileSourceSchemestring

The file source scheme to determine where the blueprint document is located.

This can be one of the following:

  • file: The blueprint document is located on the local file system of the Deploy Engine server.
  • s3: The blueprint document is located in an S3 bucket.
  • gcs: The blueprint document is located in a GCS bucket.
  • azureblob: The blueprint document is located in an Azure Blob Storage container.
  • https: The blueprint document is located via a public HTTPS URL.

For remote source authentication, the Deploy Engine server will need to be configured with the appropriate credentials to access the remote source. Authentication is not supported for https sources.

Possible values: [file, s3, gcs, azureblob, https]

Default value: file
Example: file
directorystringrequired

The directory where the blueprint document is located. For file sources, this must be an absolute path to the directory on the local file system of the Deploy Engine server. An example for a file source would be /path/to/blueprint-directory. For s3, gcs and azureblob sources, this must be the path to the virtual directory where the first path segment is the bucket/container name and the rest of the path is the path to the virtual directory. An example for a remote object storage source would be bucket-name/path/to/blueprint-directory. For https sources, this must be the base URL to the blueprint document excluding the scheme. An example for a https source would be example.com/path/to/blueprint-directory.

Example: /path/to/blueprint-directory
blueprintFilestring

The name of the blueprint file to be used during deployment. The source file is needed in addition to a change set ID as it is required as a part of the update deployment process for resolving substitutions that can only be resolved at deploy time and is required for deployment orchestration.

Default value: project.blueprint.yml
Example: project.blueprint.yml
rollbackbooleanrequired

If true, the blueprint instance update will be treated as a rollback operation for the previous update to the blueprint instance.

Default value: false
Example: false
UpdateBlueprintInstancePayload
{
  "changeSetId": "a471bbb8-1267-4e65-873b-fa86bca71fcf",
  "fileSourceScheme": "file",
  "directory": "/path/to/blueprint-directory",
  "blueprintFile": "project.blueprint.yml",
  "rollback": false
}