Azure-ARM source provider be able to auto increment the shared_image_gallery_destination image_version

[DevopsMercenary]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Please search the existing issues for relevant feature requests, and use the
reaction feature
(https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)
to add upvotes to pre-existing requests.

Description

When creating and adding a new Azure ARM image to an existing shared image gallery, it would be nice to be able to have packer determine the 'latest' version ( 1.0.1 ) and auto increment the source.arzure-arm.image.shared_image_gallery_destination.image_version to be automatically incremented by one ( 1.0.2 )

Image_Version must be in 'semantic version pattern' therefore I don't see a way to always generate unique version.

Use Case(s)

Any relevant use-cases that you see.

Potential configuration

Potential References

[DevopsMercenary]

Sorry, Created in wrong project.

[DevopsMercenary]

hashicorp/packer-plugin-azure#447