Fix: env0_configuration_variable import docs #1045
Open
Conversation
This file contains hidden or 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
lkanerv
commented
May 6, 2025
| resource "env0_configuration_variable" "project_var" { | ||
| name = "project_var_name" | ||
| value = "project_var_value" | ||
| project_id = "project_var_id" |
There was a problem hiding this comment.
Note that this differs from the API arg described in the import config
lkanerv
commented
May 9, 2025
There was a problem hiding this comment.
There is no need to run this, there's an automated github action that updates the docs
|
Ah, thanks for the heads up! Made my updates to the import example for the resource and regenerated the docs with tfplugindocs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue & Steps to Reproduce / Feature Request
Fix: adds clarity between provider usage and API behavior
Solution
For project-scope variable imports, makes clear that
project_idmust be defined in theenv0_configuration_variableresource block (if it is not, then the variable will get replaced and recreated as a GLOBAL variable)For
GLOBALvariables, do not provideScopeId. I initially made the mistake of passing the org ID asScopeId, which results in the following:Error: Could not find variable. Ensures that the provider docs align with the API expectations.