-
-
Save danrigsby/11354917 to your computer and use it in GitHub Desktop.
packer build packer.json 2>&1 | sudo tee output.txt | |
tail -2 output.txt | head -2 | awk 'match($0, /ami-.*/) { print substr($0, RSTART, RLENGTH) }' > sudo ami.txt |
Thanks @rafaelmagu, it worked very nicely!
I needed to grep the snapshot-id to delete it via AWS CLI. Based on @rafaelmagu answer, I created a gist that returns the snapshot-id: https://gist.github.com/stefanteixeira/ab91dfacda81bc030148
Perfect, thanks for the share.
Nice!
I've changed a little bit, based on @rafaelmagu :
packer build -machine-readable packer.json | tee build.log
egrep -m1 -oe 'ami-.{8}' build.log
cheers!
This works good too:
$ packer build -machine-readable packer.json | awk -F, '$0 ~/artifact,0,id/ {print $6}'
Just adding to @delaman, if you're doing multi-regions, you can do this to parse:
$ packer build -machine-readable packer.json | awk -F, '$0 ~/artifact,0,id/ {print $6}' | sed 's/%!(PACKER_COMMA)/\n/g'
These are nice solutions. I went with the grep
approach below, but the awk
approach is just as clean.
packer build -machine-readable ... | egrep 'artifact,0,id' | rev | cut -f1 -d, | rev
you might try the manifest
post-processor instead.
https://www.packer.io/docs/post-processors/manifest.html
It can produce a JSON file with the relevant data that looks like:
{
"builds": [
{
"name": "amazon-ebs",
"builder_type": "amazon-ebs",
"build_time": 1485460577,
"files": null,
"artifact_id": "us-west-1:ami-XXXXXXXX",
"packer_run_uuid": "cd66f925-1eb5-c43e-4370-e696a66d53aa"
}
],
"last_run_uuid": "cd66f925-1eb5-c43e-4370-e696a66d53aa"
}
With regard to the manifest file post-processor, you need to be on at least https://github.com/mitchellh/packer/blob/master/CHANGELOG.md#0110-october-21-2016, but https://github.com/mitchellh/packer/blob/master/CHANGELOG.md#0121-december-15-2016 has changes to the manifest config, so would probably be a better option.
Otherwise, you'll get a message saying that the manifest post-processor cannot be found.
(As I did!)
The Manifest output does not work, if you create your own ami (for example with the virtualbox bulder) and use the "amazon-import" post-processor, since it is just treating the build processor :(
The manifest postprocessor worked great for me:
"post-processors": [
[
{
"output": "manifest.json",
"strip_path": true,
"type": "manifest"
}
]
]
Then this chain of events will capture the ami-XXXXXX as shown by @dayer4b above.
cat manifest.json | jq -r .builds[0].artifact_id | cut -d':' -f2
I ended up using this along with manifest post processor to get the latest ami
cat manifest.json | jq -r '.builds[-1].artifact_id' | cut -d':' -f2
How can we directly export the AMI_ID to global variable?
This is old, but comes up when you search for how to get the ami id from the amazon-import post-processor. Note that the manifest will contain the AMI id, but you have to wrap the amazon-import post-processor and the manifest post-processor within the same list, or as Packer calls it, a sequence.
"post-processors": [
[
{
"type": "amazon-import",
"ami_name": "import_test",
"region": "{{ user `target_region` }}",
"s3_bucket_name": "{{ user `s3_artifact_bucket` }}",
"role_name": "{{ user `aws_vmimport_role` }}"
},
{ "type":"manifest" }
]
]
More info here: hashicorp/packer#7297
You can omit the cat command and pass the file file to jq directly or jq -r '.builds[-1].artifact_id' manifest.json | cut -d':' -f2
Gist is one of those sites where it pays to read the comments. I was able to take this and combine it with some of the above additional techniques and wrap it together in a modern AWS demonstration. Enjoy: https://gist.github.com/electrawn/be0c239e46517a859e31bf0a2496235e
Using a post-processor with jq
works as well.
jq -r '.builds[0].artifact_id|split(":")[1]' ./manifest.json
Seriously, we shouldn't have to do all this parsing of text. Packer should just have a way to spit out the ami_id in the language itself so we can use it in future build stages without having to parse arrays in json manifest files
@CodeForcer yes, definitely I agree!!!
Complete example using HCL with a manifest post-processor and the jq command from @dougireton:
packer {
required_plugins {
amazon = {
version = ">= 0.0.2"
source = "github.com/hashicorp/amazon"
}
}
}
source "amazon-ebs" "ubuntu" {
ami_name = "custom-ami-{{timestamp}}"
instance_type = "t2.micro"
region = "eu-west-1"
source_ami_filter {
filters = {
name = "ubuntu/images/hvm-ssd/ubuntu-jammy-22.04-amd64-server-*"
root-device-type = "ebs"
virtualization-type = "hvm"
}
most_recent = true
owners = ["099720109477"]
}
ssh_username = "ubuntu"
tags = {
Name = "my-app"
Os = "ubuntu-jammy-22.04-amd64-server"
}
}
build {
name = "custom-ami"
sources = ["source.amazon-ebs.ubuntu"]
post-processor "manifest" {
output = "manifest.json"
strip_path = true
}
}
Then just:
jq -r '.builds[0].artifact_id|split(":")[1]' ./manifest.json
Expected output:
ami-0dcbaf6794c89f392
But agree with @CodeForcer 2022 and packer still does not have a built-in method to spit out the id.
For multiple AWS regions, try:
jq -r '.builds[0].artifact_id' ./manifest.json | tr ',' '\n'
Why not use
packer build -machine-readable
and parse that output?I use: