-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Changes planned when no actual changes made #32849
Comments
Hi @mlcooper, The additional plan notation of We use GitHub issues for tracking bugs and enhancements, rather than for questions. While we can sometimes help with certain simple problems here, it's better to use the community forum where there are more people ready to help. Thanks! |
Here's where I could see a value to be added. It's known, clearly that the data document depends on specific resources that are changing as a result of the plan. Theoretically, it should be possible to infer "well, I'm dependent on a property which can be identified as something whose value is fixed upon creation (an ID or ARN), and won't change short of the resource being recreated (which the plan would be aware of, vs a change). Since the data document is ONLY dependent on fixed properties of resources that are changing, it could skip the re-evaluation of the data resource. |
@richardgavel-ordinaryexperts, if you only need to depend on the specific attributes changing, then terraform will already do what you suggest. The use of |
@jbardin I'm confused by the explanation you're trying to give in your answer. The requested feature suggests that the attributes of "ID"/"ARN" are fixed for all time. Therefore the data block should not have to change as it needs immutable attributes. The issue seems to demonstrate where the data block is not smart enough to see that those attributes do not change. In your response, you seem to describe behaviour when attributes need to change. That's the opposite of what is desired. What's the expected behaviour for a datablock when it references a resource that is being updated in place. Does the terraform plan see, on an individual resource-attribute level, which attributes are changing and which are fixed? The description of 'depends_on' behaviour seems tangential, as the code snippet above does not use that keyword. |
Thanks @jlm0x017, I think I did miss that interpretation of the original post. The output Reading more carefully here it looks like all data sources in question are directly referencing managed resources, which (unfortunately) implies the same thing as setting If there is no use of |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Terraform Version
Terraform Configuration Files
The rest of the config are resources not involved in the issue I'm having.
Debug Output
Please see Actual Behavior below.
Expected Behavior
ONLY
module.kinesis-firehose-splunk.aws_kinesis_firehose_delivery_stream.kinesis_firehose
andmodule.kinesis-firehose-splunk.aws_lambda_function.firehose_lambda_transform
would show pending changes in theterraform plan
.Actual Behavior
I can understand how
module.kinesis-firehose-splunk.aws_kinesis_firehose_delivery_stream.kinesis_firehose
andmodule.kinesis-firehose-splunk.aws_lambda_function.firehose_lambda_transform
are valid changes, but the other resources that are changing do NOT actually have any changes to make. They all say this:Output:
Steps to Reproduce
terraform plan
Additional Context
No response
References
I am experiencing the same thing happening in hashicorp/terraform-provider-aws#29393, and it was suggested there to open an issue in this repo.
The text was updated successfully, but these errors were encountered: