This tutorial will walk you through “Using resource update constraints” to a spoke local portfolio
We will assume you have:
We are going to perform the following steps:
Here are the steps you need to follow to “Using resource update constraints”
Now we are ready to add a stack to the manifest file.
Navigate to the ServiceCatalogPuppet CodeCommit repository
Click the ServiceCatalogPuppet repository
Click the link to the manifest.yaml file, and then click the Edit button
Find the spoke-local-portfolio you want to add the constraint to:
spoke-local-portfolios:
networking-options-for-spokes:
portfolio: networking
deploy_to:
tags:
- tag: "type:prod"
regions: "default_region"
Add the constraint:
spoke-local-portfolios:
networking-options-for-spokes:
portfolio: networking
constraints:
resource_update:
- products: "vpc"
tag_update_on_provisioned_product: NOT_ALLOWED
deploy_to:
tags:
- tag: "type:prod"
regions: "default_region"
When adding the constraint you can specify ALLOWED or NOT_ALLOWED as the value for tag_update_on_provisioned_product.
When specifying products you can use a wildcard to specify more than one product:
spoke-local-portfolios:
networking-options-for-spokes:
portfolio: networking
constraints:
resource_update:
- products: "vpc-with-*-subnet*"
tag_update_on_provisioned_product: NOT_ALLOWED
deploy_to:
tags:
- tag: "type:prod"
regions: "default_region"
Or you can specify a list:
spoke-local-portfolios:
networking-options-for-spokes:
portfolio: networking
constraints:
resource_update:
- products:
- "vpc-with-1-subnet"
- "vpc-with-2-subnets"
- "vpc-with-3-subnets"
tag_update_on_provisioned_product: NOT_ALLOWED
deploy_to:
tags:
- tag: "type:prod"
regions: "default_region"