-
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
New api/plan endpoint throwing errors due to trying to add status #2456
Comments
Update since a lot of investigation was ongoing in the background.
This $PLANFILE.json is then used by some of our policy checks to including module version / tags etc. When running normal PR the files including .terraform are left there until PR is either closed / applied or unlocked so they can be used by policy checks. On api calls none of those files persist (atleast looking at the pod dir straight after api plan the directory only has default configs as if it was just cloned ). Are we cleaning up the directory after plan step is done or after policy checks are done ?
|
This issue is stale because it has been open for 1 month with no activity. Remove stale label or comment or this will be closed in 1 month.' |
Hey any news on this one?
@endriu0 I don't think policy checks affect this outcome at the latest version of Atlantis. I still get the same error. |
@parmouraly no news. Feel free to propose a pr if you know of a fix and the maintainers would be happy to review 😄 |
This issue is stale because it has been open for 1 month with no activity. Remove stale label or comment or this will be closed in 1 month.' |
Community Note
Overview of the Issue
New api/plan endpoint is working and creating a plan fine but response from atlantis is 500 instead of 201. In logs I see a bunch of errors about the branch being used instead of sha for the api call :
https://github/api/v3/repos/my-org/my-repo/statuses/my-branch
Reproduction Steps
{
"Repository": "my-org/my-repos",
"Ref": "my-branch",
"Type": "Github",
"Paths": [{
"Directory": "my-directory",
"Workspace": "default"
}]
}
Logs
Provide log files from Atlantis server
Logs
Environment details
If not already included, please provide the following:
--enable-policy-checks
Atlantis server-side config file:
Repo
atlantis.yaml
file:Any other information you can provide about the environment/deployment.
Github: Github Enterprise server / Self-Hosted
Additional Context
Looks that all that needs to be done is the status-update call needs to be skipped if the call type is on api/plan / api/apply and that should hopefully stop the 500s or if we want to keep it then we should add new field to apicall for sha instead of branch.
The text was updated successfully, but these errors were encountered: