Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[HPR-1420] Remove bundled plugins from Packer core #12660

Merged
merged 4 commits into from
Oct 24, 2023

Commits on Oct 24, 2023

  1. Configuration menu
    Copy the full SHA
    e9166c8 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    05f80dc View commit details
    Browse the repository at this point in the history
  3. Remove functions for detecting plugin usage

    With the removal of vendored_plugins we are no longer interested in tacking bundled plugins usage.
    For plugins such as file, null, or anything bultin into Packer we don't track because there is no
    way to install them outside of Packer, for now.
    nywilken committed Oct 24, 2023
    Configuration menu
    Copy the full SHA
    03a3f37 View commit details
    Browse the repository at this point in the history
  4. cmd/hcl2_upgrade: Don't error when using a HashiCorp plugin that is n…

    …ot installed
    
    This change updates hcl2_upgrade to not flag known plugin components, those used for generating the required plugins
    block, when upgrading a legacy JSON template to HCL2. Any unknown plugins will be installed after running packer init
    on the generated template so we don't error. We may want to suggest running packer init to install any missing plugins.
    
    * Move knownPluginPrefixes into the hcl2_upgrade command
    nywilken committed Oct 24, 2023
    Configuration menu
    Copy the full SHA
    e57a394 View commit details
    Browse the repository at this point in the history