https://www.runatlantis.io/ logo
Join Slack
Powered by
I totally assumed the project name/lock deletion t...
# atlantis-community
s
I totally assumed the project name/lock deletion thing was included in 0.27.2
p
0.27.2 yes
it is possible that the latest tag is not pointing at the 0.27.2 patch release
so you might be using the 0.27.0
mmm no, latest is pointing to 0.27.2
@Luke Massa everything to be in place and merged to the right branch
can you share your atlantis.yaml @Steven Zhao please
and atlantis flags too
and repo.yaml config
l
Ah unfortunately I migrated laptops and forgot to bring over my test config for atlantis 😞 I will try to reconstruct it though
s
Sure, let me redact a little intelligently and get to you ASAP.
d
It’s not a full fix, maybe we should have communicated it better
It didn’t use project name at all previously, now it will if it’s set. However, the support for project name in the rest of the codebase isn’t there. So the project name is only set if you do it manually in the repo.yaml
I plan on working on full support for 0.28
s
Got around to redacting the atlantis.yaml in our project root directory 🙂 File is attached. For the parts that use 'stacks', we have an internal tool that preprocesses configs and directories and adds them to the atlantis yaml file. An earlier open source version is here: https://github.com/cisco-open/stacks/tree/main
atlantis_debug_file.yaml
@Dylan Page, that makes a lot of sense. I think that could be it - looking at our logs from 0.26 right now and comparing.
👍 1
d
@Steven Zhao fully supporting project names within the autodiscovery is my top priority the next release. Most likely we will default to the relative path of the directory
s
That would be with 0.28.x right?
For now, I could change our preprocessor (stacks) to add the project name to the Atlantis.yaml. That seems like the path of least resistance here
👍 1
d
Yes, it would be with 0.28.x
🙌 1
s
Got it, @Dylan Page. Does my plan for adding in the projectName (i.e. 
-name: my_favorite_project
etc) seem more or less sound, based on the atlantis.yaml linked?
d
@Steven Zhao Sorry for missing your reply, just it does seem more sound based on your atlantis.yaml
n
@Steven Zhao can I get some ideas on how you got around this issue? I'm currently experiencing it and I have the 
-name: my_project
entry in my atlantis.yaml file.
I'm getting the no such file or directory error when I unlock my plan
p
which version of atlantis?
n
v0.27.2 (latest)
p
did you upgrade recently?
n
Yes...
p
if you have old prs and you upgrade you will get this error still
you will need to close the PR and reopen
that way Atlantis can do a fresh clean checkout now with the workspace tree etc
n
Lemme go verify dates. Although the upgrade to the latest version was done more than 10 days ago.
Yeah...upgrade happened more than 10days ago, PR was 5days ago.
p
in your Atlantis.yaml do you have project names?
n
Yes. We actually have multiple atlantis.yaml files for different projects but yes, each project has entries for project name like so: 
-name: project_name
followed by 
dir: dir_name
p
mmm you should not have this problem with 0.27.2
n
I noticed, however, that it still releases locks even though it says failed to delete PR locks
p
so, you still have a problem, or not?
n
I'm not blocked from planning on other PRs. I guess I'm okay...although the failed to delete PR locks is a little misleading.
p
yes, it definitely is
n
Thanks for indulging me...
p
no problem
Open in Slack
PreviousNext
Powered by