|
| 1 | +--- |
| 2 | +fixes: |
| 3 | + - | |
| 4 | + Fixed compatibility with Packer 1.11.x by adding explicit plugin |
| 5 | + declarations to all template files. Packer 1.11.x introduced stricter |
| 6 | + plugin validation requiring all plugins to be declared in |
| 7 | + ``required_plugins`` blocks. |
| 8 | +
|
| 9 | + Updated templates with required_plugins blocks: |
| 10 | +
|
| 11 | + - builder.pkr.hcl (openstack, docker, ansible) |
| 12 | + - docker.pkr.hcl (openstack, docker, ansible) |
| 13 | + - devstack.pkr.hcl (openstack, docker, ansible) |
| 14 | + - devstack-pre-pip-yoga.pkr.hcl (openstack, docker, ansible) |
| 15 | + - windows-builder.pkr.hcl (openstack, ansible) |
| 16 | + - builder-aws.pkr.hcl (amazon, ansible) |
| 17 | + - docker-aws.pkr.hcl (amazon, ansible) |
| 18 | +
|
| 19 | + This fix maintains backward compatibility with Packer 1.9.x and 1.10.x |
| 20 | + while ensuring builds work correctly with Packer 1.11.x and future |
| 21 | + versions. The GitHub Actions workflow already includes the necessary |
| 22 | + ``packer init`` command to download plugins. |
| 23 | +
|
| 24 | + Added .packer.d/ directory to .gitignore to exclude plugin cache. |
| 25 | +upgrade: |
| 26 | + - | |
| 27 | + No action required for existing deployments. All changes are backward |
| 28 | + compatible with Packer 1.9.x and 1.10.x. If upgrading to or using |
| 29 | + Packer 1.11.x, ensure ``packer init`` is run before ``packer build`` |
| 30 | + or ``packer validate`` to download the required plugins (this is |
| 31 | + already handled in the CI/CD workflow). |
0 commit comments