generated from hashicorp/packer-plugin-scaffolding
-
Notifications
You must be signed in to change notification settings - Fork 40
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
makefile: remove old docs targets #155
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Since we moved the docs to integrations, we don't need to build the docs.zip file anymore, and to make it easier for plugin developers we move the logic for building the new .docs directory to the `generate' Makefile target.
Since the workflow relies on the build-docs target existing in the Makefile to ensure we don't commit a change without calling it, and since we removed it in the previous commit to fold it in generate, we don't need it anymore so we can remove it. Since the `make generate' call is already required if modifying the docs, and we check that during validate, this is safe to remove.
Since we have merged `build-docs' with `generate', we don't need to manually invoke `packer-sdc renderdocs' before the old build-docs.
When the docs were modified last, the web-docs weren't updated, and the action did not trigger on that branch, leading to the pipelines failing after that, so we fix this issue now.
lbajolet-hashicorp
force-pushed
the
fix_makefile_integration_docs
branch
from
September 21, 2023 20:51
1d76ff0
to
43298c6
Compare
Since the ci-make-docs target is no longer part of the Makefile, we cannot rely on it for making the latest docs, and therefore we must remove that from the goreleaser file too.
The docs.zip file should not be part of the release as it is no longer generated nor required to build the docs for a plugin. Keeping this in the releaser config caused the release to fail before the artifacts were updated, leading to a corrupted release.
lbajolet-hashicorp
force-pushed
the
fix_makefile_integration_docs
branch
from
September 26, 2023 20:20
1042a56
to
88ec2ae
Compare
nywilken
approved these changes
Oct 10, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Since we moved the docs to integrations, we don't need to build the
docs.zip file anymore, and to make it easier for plugin developers we
move the logic for building the new .docs directory to the `generate'
Makefile target.