-
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
beanstalk environment change output format #7517
Comments
Here is an example of the output that is shown from a beanstalk diff:
As you can see, its basically impossible to find what is ACTUALLY changing. But its this:
|
FYI - As a workaround, I pipe plan outputs through the below grep. It cuts the output down to the actual changes. |
This is a duplicate of #5179. That PR looks like a good start, crossing my fingers. I wish I had time to help out. |
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. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
When planning or applying a change to aws_elastic_beanstalk_environment resources, the output displayed to the user is generally very long.
I understand why all of the setting values need to be displayed, even if they are not changing, however it makes it very hard to pick out and verify the setting values that are actually changing.
Would it be possible to highlight the fields that are actually changing?
Maybe organize the list so that non-identical entries are at the top.
Or set identical entries to a grey color.
The text was updated successfully, but these errors were encountered: