-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Proof of concept: more concise/useful comments #1325
Proof of concept: more concise/useful comments #1325
Conversation
Hello @raxod502-plaid, thank you for the contribution! I would be interested in getting the community feedback before we proceed with this one as it is a fairly substantial change to the look and feel of the comments from atlantis. A large number of our e2e tests assert against the specific outputs in the current format so we will need to bring them in line with the new format before we can move forward with this PR. The new format is a big 👍 from me but let's hold off until we can gather some more feedback. |
Yes, of course. This PR changes things all over the place that would reasonably be controversial and I expected to need a community discussion about the desired output format. And yes, I didn't update any of the tests yet. |
I really like this idea. Every now and then, I end up with a PR that will run a plan on 500ish modules, and scrolling through all of the plans with no changes is less than ideal |
I really like the summary and the details parts. The color coding.. not so much but it is acceptable at least. |
Feels kind of related: #1267 |
The color coding should probably be optional. |
What would be needed to get this into a mergeable state? Would love to see this and happy to help if I somehow can :-) |
I really like this idea moving forward - it would help us see what's actually changing as part of MR/PR comment(s) |
I'm in favor of the color coding 💯. Others have asked for this as well such as: #1395 W.r.t to the output restructure, i definitely like it better than what's there currently. However, I know we've been talking about making these templates configurable for anyone running Atlantis. Though I'm unsure of when we'll get around to something like that. Either way in order to get this to a mergeable state we basically just need to fix all the tests and change their fixtures which is quite a bit of work.... if anyone is up for it 😅 |
@raxod502-plaid is this relevant still? thanks. |
Yes, unless #1751 did more than I was aware of. |
can you check @raxod502-plaid ? and if so update the PR description with the differences? ( and code if necessary) |
Looking at the diff for the linked PR, only |
ok, good so if you fix the conflicts I will ask for another review. |
Conflicts fixed. |
@raxod502-plaid could you check the errors? |
Before I update tests, can somebody confirm that the changes are acceptable? No point in changing tests if changes are requested about the output format, since then the tests will have to be changed again. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This pull request makes available a number of internal changes that we have made to Atlantis at my workplace in order to make Atlantis' comments more useful and readable. I cannot guarantee that I will have the bandwidth to maintain the PR (in particular, it kind of tramples on some existing Atlantis features that we don't use at my workplace), but I thought I would make it available for the community to build upon.
add summary at top of comment
Before:
After:
always use <details> tag for output, when available
Avoids this kind of inconsistency which hinders readability:
color-code more aggressively
Before:
After:
summarize nested property updates
For example, from the Terraform plan
we would get a summary as such, where the specific properties within the modified objects are enumerated.
Modify 1 (modified properties: add 3)