-
Notifications
You must be signed in to change notification settings - Fork 14
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
Configuration Variable defined in env0_environment resource getting "updated" in plan #756
Comments
@away168 workflow has many limitations concerning to the terraform provider especially because many of the configurations are coming from a yaml file. Where are the "sub_environment_configuration" entries? Notice the following comment: I'm wondering where these variables are coming from? |
@TomerHeber we're not using subenvironment configuration variables - just defining configuration for the entire workflow. In the UI, you can define Environment Variables that would be applied to all sub-environments). In this particular case, we're defining a Terraform Variable for all sub-environments. |
@away168 makes sense. What are all these configuration changes? where is it coming from? |
@TomerHeber the screenshot is a more complete code, I only copied and pasted one configuration variable, when the customer in fact has 8 or 9 configuration variable in his code. |
Discussed in Slack: |
Describe the bug
Using
env0_environment
withconfiguration
block - on a plan - the configuration block is being recreated.To Reproduce
FWIW: this is a workflow template - creating terraform configuration variables.
Expected behavior
Plan should show no changes after initial deployment.
Provider Version
1.16.0
Screenshots
Additional context
Template type is a Workflow type.
The text was updated successfully, but these errors were encountered: