Please vote on this issue by adding a đź‘Ť reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
I suggest in case the user was not authorised, to add an Info log with the commands run and the output. (The echo from the script.)
Describe the drawbacks of your solution
I'm not sure how comfortable people are with logging the commands run and the output. I think common sense applies—don't echo anything sensitive.
Describe alternatives you've considered
Status quo. Try to debug the script by running it locally and feeding in the variables manually. But this is currently not enough, as for the issues I face, I need to see the actual arguments Atlantis is feeding to the script.
Community Note
Describe the user story
As a developer, when I use Repo and Project Permissions: External Command (https://www.runatlantis.io/docs/repo-and-project-permissions.html) I'd like to be able to debug the external script I wrote.
Describe the solution you'd like
I suggest in case the user was not authorised, to add an Info log with the commands run and the output. (The
echofrom the script.)Describe the drawbacks of your solution
I'm not sure how comfortable people are with logging the commands run and the output. I think common sense applies—don't echo anything sensitive.
Describe alternatives you've considered
Status quo. Try to debug the script by running it locally and feeding in the variables manually. But this is currently not enough, as for the issues I face, I need to see the actual arguments Atlantis is feeding to the script.