Hello Packer Friends, Discovered packer not long ago, started utilizing it in my tooling to produce an AMI inside of AWS for auto scaling. The use case that I currently have included some provisioning scripts that I keep in a provision dir, as well as some supporting application files that I keep in a files dir. I am not so worried about the provision dir, no secrets in this dir, however my files dir holds numerous application configs with numerous secrets. I am looking for the packer way of protecting these files in source, then un-encrypt once checked out to actually run my packer build commands to build my images from my laptop.
Looking for the sage wisdom I know this group can provide, it's much appreciated. -Aaron. -- 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/mitchellh/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 packer-tool+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/3a047093-bff8-4df3-b193-4d82c6970744%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
