This change adds a new set of maps for builders, provisioners, and
post-processors that store reference to components that were once part
of Packer and are now vendored. This file acts as a single place for
defining this vendored components, which are then merged into the main
components maps to be used in Packer.
Quick test to ensure the exoscale-import post-processor is still loaded
```
// Validate that exoscale-import is in the know post-procoessors list
~> packer.test build docker_centos_shell_provisioner.pkr.hcl
Error: Unknown post-processor type "badlynamed-import"
on docker_centos_shell_provisioner.pkr.hcl line 18:
(source code not available)
known post-processors: [ucloud-import digitalocean-import docker-push
googlecompute-export manifest vsphere-template docker-tag vsphere checksum
docker-import exoscale-import yandex-export compress googlecompute-import
yandex-import vagrant-cloud alicloud-import amazon-import artifice shell-local
docker-save vagrant]
// Validate that exoscale-import get loaded
~> packer.test build docker_centos_shell_provisioner.pkr.hcl
Error: Failed preparing post-processor-block "exoscale-import" ""
on docker_centos_shell_provisioner.pkr.hcl line 18:
(source code not available)
4 error(s) occurred:
* api_key must be set
* api_secret must be set
* image_bucket must be set
* template_zone must be set
==> Wait completed after 2 microseconds
==> Builds finished but no artifacts were created.
```
This change will vendor the new version of the exoscale-import
post-processor component, but remove all of its code from Packer. After
the v1.8.0 release this change should be removed entirely.
This vendor process is being used as a workaround for decoupling the
exoscale-import component without causing a breaking change in Packer.
Users of Exoscale are encouraged to leverage `packer init` for
installing the latest version of packer-plugin-exoscale.
This change removes the generation of command/plugin.go so that plugin
registration can be managed manually. As we begin to break out plugins
we will need to begin modifying this file, possibly with stubs to allow
for the removal of plugins without breaking Packer's backwards
compatibility with 1.7.0. After 1.8.0 is released we should be able to
revet these changes so that we can continue to generate the plugin
file for those plugins core to Packer.
* Fix syntax in BlockDevice JSON example
Keys must be quoted in JSON.
* Update comment to match generated docs
Co-authored-by: Wilken Rivera <dev@wilkenrivera.com>
* Add local components to build on new DocsPage functionality.
* Add new nav-data format, and placeholder remote-plugins config
* Bump to pre-release components and implement remote loading
- Migrates /docs to new DocsPage API, and adds remote plugin loading functionality
- Migrates /guides and /intro to new DocsPage API
* Remove now unused JS nav config
* Cut empty comment line
* Update to v3.21.1 to allow builds to work for darwin arm64
Co-authored-by: Megan Marsh <megan@hashicorp.com>
Co-authored-by: Adrien Delorme <adrien.delorme@icloud.com>
While trying to get packer to:
1. Assume a role
2. use `auto` price for spot instances
2. Assign an instance profile to the provisioned instance, I hit this error:
```
The provided credentials do not have permission to create the service-linked role for EC2 Spot Instances.
```
Adding the `iam:CreateServiceLinkedRole` entitlement to the role that packer assumes was all I needed to do.
Megan Marsh
Wilken Rivera
Marc Falzon
Tasha Marreiros
Kris Fremen
Thomas Dreibholz
Kennith Leung
Hosh
Sylvia Moss
Forrest C. Shields II
Jiankun Lu
Zachary Shilton
Kyle MacDonald
Blake Garner
Brian Farrell
Alvaro Miranda Aguilera
kiddom-kq