-
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
Atlantis api/plan
returns status 500
#5322
Comments
Hey @Exchizz, I'm here to help you with any bugs, questions, or contributions! I found a similar open issue titled API POST requests 500 Internal Server Error, which was last updated on September 29, 2024. However, this issue has no comments or references, so it might not provide additional insights into your problem [1]. Regarding your issue with the To troubleshoot, ensure that the Additionally, the issue might be linked to changes introduced in pull request #5242, which could have affected the behavior of the To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other | Bug Report |
Thanks for this @Exchizz. I'm looking at why this wasn't picked up in the tests, and this has exposed lots of other issues with the plan and apply APIs. Be aware that they are really only 'alpha' quality. |
Community Note
Overview of the Issue
I'm trying to use Atlantis' plan API but it returns 500 and no information about what happened. Atlantis with debug log enabled doesn't reveal anything about what's causing Atlantis to fail.
Reproduction Steps
I'm calling the plan API with the following command:
Logs
Environment details
Additional Context
I can't get it to work with Atlantis
v0.32.0
but it fails with versionv0.33.0
andmain
. I've run atlantis with vs codes's debugger, and it fails when trying to execute the next step:https://github.com/runatlantis/atlantis/blob/main/server/controllers/api_controller.go#L190
If I comment out the lines above, Atlantis runs the plan successfully. From git blame, the code shown above might be related to this PR: #5242
The text was updated successfully, but these errors were encountered: