Migration plugin docs to integration framework #73
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
👋 fellow Packer maintainer working on migrating your plugin to the Packer integration framework.
This change takes the necessary steps to register this plugin as an official Packer integration.
Integrations can be found on the Packer integration portal at https://developer.hashicorp.com/packer/integrations.
The pull-request consists of the following changes:
metadata.hcl
for registering the plug-in and it components as integrations.Details on the contents, along with a description of the attributes, can be found at https://github.com/hashicorp/integration-template.
.web-docs
directory for serving the fully render documentation as the integration docs.make build-docs
for syncing changes to thedocs
directory to the.web-docs
directory.Changes to the integration docs can be made at plugin release via the
notify-integration-release-via-tag
workflow ormanually by running the
notify-integration-release-via-manual
workflow.Details on how the Integration framework pipeline works can be found at hashicorp/packer#12702
TODOs
.web-docs/metadata.hcl
.