hashicorp / hashicorp/packer-plugin-azure
Packer-azure_arm: Use latest custom managed image name as source image
- Dominant language
- Go
- Stars
- 63
- Forks
- 103
- PR merge metrics
- No merged PRs in 30d
Description
_This issue was originally opened by @shriganeshs as hashicorp/packer#5731. It was migrated here as a result of the [Packer plugin split](https://github.com/hashicorp/packer/issues/8610#issuecomment-770034737). The original body of the issue is below._
Similar to the following way provided for amazon_ebs builder
```
"source_ami_filter": {
"filters": {
"name": "*custom_centos7_python36*"
},
"most_recent": "true"
}
```
How can I get the latest source image `custom_managed_image_name` for Azure?
I will be storing images with name as `custom_centos7_python36_{{timestamp}}`, and I want to use the latest image as source image for new Packer build.
- Packer version 1.1.1
Contributor guide
Research direction
The issue names no file, test, or entry point. Start by locating the Azure builder configuration for the source managed image and verify how a name pattern can select the newest image; done means a Packer build uses the latest matching custom image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100