-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(ubuntu):Add an amazon-ebs
AMI builder
#1447
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Updatecli check fails: as the manifest assumes the code is on the principal branch, either you add it on a subsequent PR or we can accept it's working once merged (but you'll have to test it locally without the
scmid:
keys) - We must use environment variable for the AWS provider setup. Please read carefully https://developer.hashicorp.com/packer/integrations/hashicorp/amazon#environment-variables and https://developer.hashicorp.com/packer/integrations/hashicorp/amazon#static-credentials and mùake sure you get the difference (see suggestions): it's a blocker
Co-authored-by: Damien Duportal <damien.duportal@gmail.com>
Update:
Since windows AMI image source logic is not included in this PR, the windows agent builds are failing in
I believe the problem is with Further steps will include exporting the aws credentials and region for terraform-packer-user as environment variables instead of using static variables. |
Signed-off-by: jayfranco999 <jaideepfrancis999@gmail.com>
Signed-off-by: jayfranco999 <jaideepfrancis999@gmail.com>
@jayfranco999 Proposal for a clear title:
instead of:
WDYT? |
amazon-ebs
AMI builder
As per jenkins-infra/helpdesk#4353 (comment)
Related to jenkins-infra/helpdesk#4316 (comment)
This PR introduces the following to packer-images: