-
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
/api/plan does not create workspace if it does not exist #2949
Comments
For reference, the pr that implemented the /plan endpoint is PR #997 by @remilapeyre and then by @lilincmu. It's also quite possible that if the /plan route doesn't work for workspaces, that the /apply route may not either. From the error, it looks like it's looking in the wrong directory for the file.
|
Hi, I'm seeing this problem as well in 0.22.2, for me it occurs when a directory targeted plan is run:
result:
logs:
Workaround:
|
Will this be addressed in the latest build? |
if someone created a PR with the fix, yes
…On Wed, Feb 15, 2023, 9:25 a.m. Alan Lee ***@***.***> wrote:
Will this be addressed in the latest build?
—
Reply to this email directly, view it on GitHub
<#2949 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQ3ERHGXO5TMQH53TLVFCDWXUGQNANCNFSM6AAAAAATUJGTIE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Did you figure out a workaround for this? Looking to replicate drift detection for gitlab or add gitlab support directly and hitting this when using the API. In some cases even with an existing PR so wondering if I'm just using it wrong.
|
I will be reviewing this week. |
@GenPage any updates? |
See #3584 (comment) I'm hesitant to merge until we understand the problem with locks as detailed in ADR 0002 #3345 The last thing we want to do is call to clone/workspace in its current regressed state. |
Got it, thanks for the clarity. Unfortunately, this is blocking us from upgrading to newer versions of Atlantis because it keeps hitting the |
I think this will not get merged, it is just a matter of time before we fix the locks problem that has caused a lot of issues. |
I'm running into this issue as well, I was trying to use |
Community Note
Overview of the Issue
when using the new
/api/plan
API and sending a request I get a 500 Internal server error due to the PR+workspace does not exist.Reproduction Steps
send a request to the altantis server with this payload:
Logs
Server Logs
Environment details
Atlantis server-side config file:
Repo
atlantis.yaml
file:Additional Context
Trying to implement drift detection
The text was updated successfully, but these errors were encountered: