Lucas Bajolet 682968d0df packer: don't load plugins with metadata in name ...

If a plugin is installed in the PACKER_PLUGIN_PATH, and its version
contains metadata, we reject it. This is because metadata is free-form
data, which could then make it possible to have multiple conflicting
versions of a plugin installed, so we don't support it and explicitely
reject plugins like those.

A valid plugin with metadata in its version information should be
installed without its metadata part, so there can only be one variant of
the plugin installed at a specific version.

2024-05-16 13:03:29 -04:00

..

github

packer: relax constraints on sources

2024-04-29 14:28:24 -04:00

testdata

plugin-getter: don't rely only on version for list

2023-12-05 09:55:18 -05:00

checksum.go

[COMPLIANCE] License changes (#12568)

2023-08-10 15:53:29 -07:00

docs.go

[COMPLIANCE] License changes (#12568)

2023-08-10 15:53:29 -07:00

plugins_test.go

addrs: return error on ParsePluginSource

2024-05-14 14:47:06 -04:00

plugins.go

packer: don't load plugins with metadata in name

2024-05-16 13:03:29 -04:00