-
Notifications
You must be signed in to change notification settings - Fork 3
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
parse outputs changes #4
Comments
Hey @rvoitenko, let me take a look at it and get back to you as soon as I can! |
Hello @rvoitenko Sorry for the time, I haven't been able to review this feature before. Looking at the library, it seems that it would be possible to show the changes in the outputs. I need to research more about it, I will try to get a new release out as soon as possible :) |
@containerscrew You may want to have a look at my current branch: I have this functionality, but its terrible code quality wise. That said, this branch has been in production for the past four months, being used hundreds of times per day on many different repositories. You may also want to copy a few things from my bash function. Terraform plan locks remote state, so if you throw away the plan file, you end up with locked remote state. My bash function addresses this. |
@containerscrew, @danielewood why is this issue marked as completed? I've tested it:
|
Hi @rvoitenko . Let's see if I understood you correctly. Imagine you are declaring the following:
https://registry.terraform.io/modules/terraform-aws-modules/lambda/aws/latest?tab=outputs. Imagine the URL change, so the output of that lambda changes because its URL has changed. Do you want it to also be reflected in the |
Yes, exactly. Because changes in outputs can be crucial in some cases. Currently I have to do some dirty hack with bash to add output changes to summary:
So it would be much nicer if tftools can add output changes to summary. |
Hi!
not an issue, more a proposal/question.
Do you think it would be difficult to parse "Changes to Outputs:" from the plan as well?
It's also an essential part of terraform plan information.
The text was updated successfully, but these errors were encountered: