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회 조회
답변 없음

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠