Re: [packer] Packer v1.5.0 has been released

2019-12-19 Thread Gautam Singh 
Congratulations on new release. Thanks for adding support for HCL2. Can't
wait to play with it.

Thank,
Gautam

On Wed, Dec 18, 2019, 7:01 PM Megan Marsh  wrote:

> Hello Packer community!
>
> We're very pleased to announce the release of Packer v1.5.0, the last
> release of 2019.
>
> *It contains two major new features: *
>
> First, you can use HCL2 instead of json to define your Paceker templates,
> if you decide you would like to. If you don't want to mess with your
> templates, don't worry! We won't be deprecating json templates any time
> soon. Here is some documentation and examples to get you started:
> https://www.packer.io/guides/hcl
>
> Second, special connection information like host and port of the
> provisioning instance, are now shared between builders and provisioners.
> You can access them using golang's templating engine. See the docs for
> details and an example:
> https://www.packer.io/docs/templates/engine.html#build
>
> We also have a bunch of bug fixes and minor improvements.  For full
> details, see the changelog:
> https://github.com/hashicorp/packer/blob/master/CHANGELOG.md#150-december-18-2019
>
>
> *There are two small backwards incompatabilites for everyday users:*
>
> - The "clean_ami_name" template engine is now fully deprecated. Use
> "clean_resource_name" instead.
> - The ansible-local "galaxycommand" option has been renamed to
> "galaxy_command".
>
> For both of these incompatabilities, calling `packer fix` against your
> template will output a template with the necessary changes made so that you
> do not have to search for the fields to correct.
>
> *There are some larger backwards incompatabilities for plugin maintainers*
> .
>
> Plugin maintainers will see that the interfaces of builders, provisioners,
> and post-processors have changed.
>
> These changes are noted in the documentation for third party plugins;
> please refer to those documents to get your plugins back up to speed with
> the latest version of the Packer core.
>
> As always, please reach out to us via the GitHub issue tracker if you find
> anything wrong.
>
> We're really excited about the improvements that these changes will bring
> to the tool. Thanks for being such a great community to work for, and we
> hope you have a wonderful holiday season, no matter which ones you
> celebrate.
>
> Thanks
> Megan and the Packer team
>
> --
> 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/93d17630-badf-4788-aab2-8c5dddfc2472%40googlegroups.com
> 
> .
>

-- 
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/CAA7kr8AVgnZau4oN4eomut-4OsFEh9RGBehTQAq%2BG7KMDCVaXg%40mail.gmail.com.

Re: [packer] Packer v1.5.0 has been released

2019-12-19 Thread Megan Marsh 
Quick update about the v1.5.0 release -- we just incorporated OSX code
signing into our release, and as a result of a mistake where I calculated
the checksums _before_ signing the OSX binaries, the current checksums for
darwin are wrong. I am pushing up a corrected checksums file and signature
now; the binaries themselves are the same and users of non-osx versions of
Packer are unaffected.

Thanks!
Megan

On Wed, Dec 18, 2019 at 5:01 PM Megan Marsh  wrote:

> Hello Packer community!
>
> We're very pleased to announce the release of Packer v1.5.0, the last
> release of 2019.
>
> *It contains two major new features: *
>
> First, you can use HCL2 instead of json to define your Paceker templates,
> if you decide you would like to. If you don't want to mess with your
> templates, don't worry! We won't be deprecating json templates any time
> soon. Here is some documentation and examples to get you started:
> https://www.packer.io/guides/hcl
>
> Second, special connection information like host and port of the
> provisioning instance, are now shared between builders and provisioners.
> You can access them using golang's templating engine. See the docs for
> details and an example:
> https://www.packer.io/docs/templates/engine.html#build
>
> We also have a bunch of bug fixes and minor improvements.  For full
> details, see the changelog:
> https://github.com/hashicorp/packer/blob/master/CHANGELOG.md#150-december-18-2019
>
>
> *There are two small backwards incompatabilites for everyday users:*
>
> - The "clean_ami_name" template engine is now fully deprecated. Use
> "clean_resource_name" instead.
> - The ansible-local "galaxycommand" option has been renamed to
> "galaxy_command".
>
> For both of these incompatabilities, calling `packer fix` against your
> template will output a template with the necessary changes made so that you
> do not have to search for the fields to correct.
>
> *There are some larger backwards incompatabilities for plugin maintainers*
> .
>
> Plugin maintainers will see that the interfaces of builders, provisioners,
> and post-processors have changed.
>
> These changes are noted in the documentation for third party plugins;
> please refer to those documents to get your plugins back up to speed with
> the latest version of the Packer core.
>
> As always, please reach out to us via the GitHub issue tracker if you find
> anything wrong.
>
> We're really excited about the improvements that these changes will bring
> to the tool. Thanks for being such a great community to work for, and we
> hope you have a wonderful holiday season, no matter which ones you
> celebrate.
>
> Thanks
> Megan and the Packer team
>
> --
> 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/93d17630-badf-4788-aab2-8c5dddfc2472%40googlegroups.com
> 
> .
>

-- 
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/CAGPV1uozFtfqjvTQToHh0F8cHsaN_mQpcU-hLmkK5_c%2BXmjMHQ%40mail.gmail.com.

Re: [packer] Re: guix vagrant script stuck after reboot

2019-12-19 Thread Rickard von Essen 
It's a very big topic and largely depends on related knowledge of
networking and Linux system administration etc.

Maybe check this
https://hostadvice.com/amp/how-to/how-to-troubleshoot-ssh-issues/

Or familiarize more with Linux administration:
https://debian-handbook.info/browse/stable/

On Thu, Dec 19, 2019, 07:26 Bashid  wrote:

> what topic i must explore when it's stick in error position?
>
> you troubleshoot ssh both from the host and inside the VM
>
>
> What's you mean? is it possible to explain more?
>
> --
> 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/394077e0-1514-49af-bb2a-9279dc0e9457%40googlegroups.com
> 
> .
>

-- 
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/CALz9Rt9gzr_txfobGC%2BmR_aPbOgH%3DEPyM1C4KCQ5Msu3uiSvkQ%40mail.gmail.com.