Skip to content
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

Include the job url as a property to be used in a template #5391

Open
1 task done
cpaloia opened this issue Mar 7, 2025 · 0 comments
Open
1 task done

Include the job url as a property to be used in a template #5391

cpaloia opened this issue Mar 7, 2025 · 0 comments
Labels
feature New functionality/enhancement

Comments

@cpaloia
Copy link

cpaloia commented Mar 7, 2025

Community Note

  • 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.

Describe the user story
In certain cases, it's necessary to hide Terraform plan output in GitHub comments—such as in public repositories where the output may contain sensitive information. However, users may still need access to the plan details via a secure URL, such as one behind a firewall or ingress.

By including the job URL in the GitHub comment template (in addition to the existing GitHub check link), we provide users with clear guidance on why the output is hidden and where they can access it instead.

Describe the solution you'd like
I would like to be able to use the job url in a github comment template

Describe the drawbacks of your solution
None that I can think of

Describe alternatives you've considered
It is a small change, so not many different options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New functionality/enhancement
Projects
None yet
Development

No branches or pull requests

2 participants