CloudFormation cannot update image recipe without several version bumps

0

I have a use case in which simply updating a parameter in a CloudFormation stack would greatly simplify an image builder pipeline update process. However, I cannot do this since the ARN for things like components and image recipes are based on version and those objects are immutable. The version numbers are completely irrelevant for my use case aside from being able to find log streams from the build, but even those I don't really care about.

What I would like is for CloudFormation to either auto-increment the version number, or completely destroy the resource and rebuild it on update so that there isn't an ARN conflict, in which case I would just leave the version set to '0.0.0'.

What I have tried: UpdateReplacePolicy set to "Delete". CloudFormation reports that the resource already exists implying the new resource is being built before the old resource is deleted. Publishing a version number as an output and auto-incrementing it in the template. There doesn't appear to be a way to increment an integer in a CloudFormation template.

已提問 4 個月前檢視次數 116 次
沒有答案

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南