Hi all,
I need to block project-wide SSH keys from getting automatically added to a
temporary instance while I am building GCP images with Packer.
As far as I understand from the following links:
https://stackoverflow.com/questions/53416024/packer-doesnt-import-project-ssh-keys-googlecompute/53419490#53419490
https://groups.google.com/forum/#!searchin/packer-tool/block-project-ssh-keys%7Csort:date/packer-tool/46YGfuo58ZY/J9al336fCQAJ
I need to use the following option:
"metadata": {
"block-project-ssh-keys": true
}
I have tried it. Here is an excerpt from the code:
"name": "ubuntu-1604",
"type": "googlecompute",
...
"image_labels": {
"cookbook": "{{user `cookbook`}}",
"application": "{{user `application`}}",
...
},
"metadata": {
"block-project-ssh-keys": true
}
},
However, the project SSH keys are still added, and the users who own those
keys are still created on the temporary instance and then baked into our
image.
Could you please advise? Is it something obvious that I am missing?
Regards,
Ch.
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/hashicorp/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/packer-tool/cecc79e9-3bf9-4219-b80e-890280fd0894o%40googlegroups.com.
