In new packer versions it is possible to define required plugin in packer configuration file. This eliminates need to download the plugin locally and execute manual steps to download, chmod, etc. So this simplify whole process very much and allows users to keep exact dependency version directly in repositories.
$ packer init --upgrade default.pkr.hcl
Error: Invalid plugin type
on default.pkr.hcl line 43, in packer:
43: goss = {
44: version = "= 3.0.0"
45: source = "github.com/YaleUniversity/packer-provisioner-goss"
46: }
Plugin source "github.com/yaleuniversity/packer-provisioner-goss" has a type
with the prefix "packer-", which isn't allowed because it would be redundant to
name a Packer plugin with that prefix. If you are the author of this plugin,
rename it to not include the prefix.
Would it be possible to rename this repository to provide this? I think when renaming github repository, also the old name is preserved and redirected to new repository so this change is not that backwards incompatible.
In new packer versions it is possible to define required plugin in packer configuration file. This eliminates need to download the plugin locally and execute manual steps to download,
chmod
, etc. So this simplify whole process very much and allows users to keep exact dependency version directly in repositories.When I try to use it I use following config:
But it fails with this error:
It looks like the repository has to be renamed in order to allow this feature to work -- source: https://www.packer.io/docs/plugins#source-addresses.
Would it be possible to rename this repository to provide this? I think when renaming github repository, also the old name is preserved and redirected to new repository so this change is not that backwards incompatible.
Here is working example by using my fork https://github.com/Lirt/packer-plugin-goss/releases/tag/v3.1.2: