You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 "me too" comments, 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.
Description
Situation: Building multiple images in different Azure Tenants and publishing to a single HCP Packer Bucket. In order to do this, we must create a single .pkr.hcl file and execute a single packer build .. After a successful build, we have a need to tag the underlying images after a successful Wiz scan.
High Level Order:
packer build . for several concurrent image builds, each isolated in their own Azure Tenant.
Images are successfully built, image id's are present in the manifest.json file.
Security scan on each image.
Image scan on each image is successful.
Tag the underling images, which requires the Tenant Id and Subscription Id for authentication.
Proposal: The Azure Packer plugin should expose tenant (and optionally subscription) id to allow custom_data to contain this information for post build tasks.
Ideal Syntax:
post-processor "manifest" {
output = "manifest.json"
strip_path = true
custom_data = {
tenant_id = build.TenantID
subscription_id = build.SubsriptionID # optional, could be parsed from "artifact_id" but very help here
}
}
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 "me too" comments, 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.
Description
Situation: Building multiple images in different Azure Tenants and publishing to a single HCP Packer Bucket. In order to do this, we must create a single
.pkr.hcl
file and execute a singlepacker build .
. After a successful build, we have a need to tag the underlying images after a successful Wiz scan.High Level Order:
packer build .
for several concurrent image builds, each isolated in their own Azure Tenant.manifest.json
file.Current: The Azure Packer plugin (https://github.com/hashicorp/packer-plugin-azure) currently exposing a single Build variable -> https://developer.hashicorp.com/packer/integrations/hashicorp/azure/latest/components/builder/arm#build-shared-information-variables called "SourceImageName".
Proposal: The Azure Packer plugin should expose tenant (and optionally subscription) id to allow custom_data to contain this information for post build tasks.
Ideal Syntax:
Would result in:
Potential References
An existing build property is exposed called "SourceImageName" -> https://developer.hashicorp.com/packer/integrations/hashicorp/azure/latest/components/builder/arm#build-shared-information-variables
The text was updated successfully, but these errors were encountered: