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

Add path attribute to required plugins #12641

Closed

Conversation

lbajolet-hashicorp
Copy link
Contributor

No description provided.

The required_plugins parse tests define a `want_diags' flag, but don't
actually use it in subtests, so if one was to add a test that is
expected to produce errors on this step, this would always fail.
In order to let users circumvent the plugin loading mechanisms for
loading plugins specified in the `required_plugins' blocks, we add a new
`path' attribute to the plugin specifiers.

Specifying this attribute makes it so that loading the plugin
circumvents completely the checks in place for a required plugin
(version, source), and forcefully loads the plugin from the specified
path.

That being said, this is not a reliable long-term solution for this kind
of problem, as it makes it harder/impossible to share the template, as
the path must resolve in order for the build to proceed, and this is
environment-bound.
@lbajolet-hashicorp lbajolet-hashicorp requested a review from a team as a code owner September 28, 2023 16:21
@lbajolet-hashicorp
Copy link
Contributor Author

Note: this is reviewable as-is, but we should probably wait until I write more tests for it, I'm not sure how to proceed because of the plugins' dependency, but I'll figure it out

@lbajolet-hashicorp lbajolet-hashicorp marked this pull request as draft October 10, 2023 14:40
@nywilken nywilken added enhancement stage/needs-discussion stage/thinking Flagged for internal discussions about possible enhancements and removed stage/needs-discussion labels Oct 23, 2023
@nywilken
Copy link
Contributor

nywilken commented Dec 5, 2023

Closing in favor of #12643 - but keeping the branch around for historical purposes should we need to revisit.

@nywilken nywilken closed this Dec 5, 2023
Copy link

github-actions bot commented Jan 5, 2024

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement stage/thinking Flagged for internal discussions about possible enhancements
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants