Open roman-agentic opened 3 years ago
Not sure if this issue is related, but we had the update tags constraint disabled on all our products. We recently enabled tag updates by adding the constraint; however, it appears to only apply to newly created provisioned products. We did notice that if we manually perform a stack update in the console by adding another tag, the tags appear to be pushed to the provisioned product.
Hi, Unless I misunderstood you are requesting to "force" updates on provisioned products, which might be unexpected or unwanted for your users. I understand that Service Catalog is supposed to be a catalog of "in-house products you offer"to your users but you don't necessarily manage these on their behalf.
Not sure if this is a CloudFormation or Service Catalog limitation.
Basically, initially when deploying a CloudFormation stack the tags are applied to your portfolio, but if you make updates to the stack, such as a tagging change, these tags are not reflected on the portfolio.
Service Catalog has a feature to manage and propagate tags from the portfolio/product level, known as TagOptions. This however, only applies when a provisioned product is first created, or when it is updated (and only if the tag update constraint is enabled on the portfolio).
Updating the TagOptions on a portfolio or product will unfortunately not trigger an update on already provisioned products, and will require an update to be performed on the provision product side.
I would like to be able to have CloudFormation tag updates be applied to my Service Catalog Portfolio, so that I can manage my tagging through a CloudFormation stack and changes to this stack will update the tagging on the Service Catalog Portfolio.