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

Adding jobs url to the plan api response #5107

Open
1 task
andrewkaldani30 opened this issue Nov 19, 2024 · 0 comments
Open
1 task

Adding jobs url to the plan api response #5107

andrewkaldani30 opened this issue Nov 19, 2024 · 0 comments
Labels
feature New functionality/enhancement

Comments

@andrewkaldani30
Copy link

andrewkaldani30 commented Nov 19, 2024

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
For context, I am working on a dirft detection service for our atlantis directories. Ideally, we'd send a slack message of projects that were changed along with a link where they can view the plan. It would be fairly easy to do this if the job url was provided in the plan response. .
Describe the solution you'd like
Similar, to providing the lockUrl provide the jobs url

Describe the drawbacks of your solution

Describe alternatives you've considered

@andrewkaldani30 andrewkaldani30 added the feature New functionality/enhancement label Nov 19, 2024
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

1 participant