-
Notifications
You must be signed in to change notification settings - Fork 440
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
fix: Graceful failures when using cdktf
with non-admin tokens
#2258
Conversation
1aa71fc
to
c671f81
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a good first step at improving the permissions problem (given the current way things work).
And, as soon as we implement #1955, we should get a printed plan for those non-admin users, too 👍
857f0d4
to
22a2c0f
Compare
22a2c0f
to
a3160bc
Compare
…in outputs when token lacks permissions
1fe2c27
to
e7860c5
Compare
I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Closes: #2236
I'm still not really comfortable with the big-picture understanding of how we use
json-output
. While this PR works well enough, please let me know if there are certain scenarios that are broken because of this. Especially around cross-stack references and so on.