-
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
"invalid key" for all job urls #2111
Comments
cc @jvrplmlmn Any idea? |
Unfortunately not, we are running Atlantis on GitHub, not on GitLab, so unsure how to reproduce this one. We are hitting #2026 (or a variant of) for the empty console, which seems different than this issue, but might be tangentially related.
Are you referring to |
@jvrplmlmn It's odd that this would work on GitHub but not on GitLab, or is job generation/validation tied to platforms?
This is happening on v0.18.5 but also in 0.19.1. |
This is also happening on GitHub, and on atlantis |
Could there be a clue in that the callstack contains GetProjectJobsWS() even though it should call GetProjectJobs() when not used with a workspace, and when the url doesn't end in
|
With Atlantis |
I am running |
hello. please set local execution mode After applying ATLANTIS_TFE_LOCAL_EXECUTION_MODE=true we are able to see the logs. ref |
Community Note
Overview of the Issue
With the latest Atlantis Gitlab jobs are now properly reported individually. When clicking on an entry this leads to Atlantis, with an entry like:
The console on the webpage however is empty. On the Atlantis server I can see an error occurring as soon as I hit the link.
Reproduction Steps
Logs
Logs
Environment details
Additional Context
The text was updated successfully, but these errors were encountered: