-
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
--hide-prev-plan-comments
flag fails if using Github App name with uppercased or space chars
#1161
Comments
In my case I was using the Fargate Module and after reviewing the inputs I noticed that the value for Setting |
I'm using the same module, latest version 2.24.0, and tried both ways, using the custom env var and the argument, but still seeing the same result. |
And yet the GitHub comments do not hide...at this point I'm questioning my sanity! 😄 |
I am using Atlantis with the GitHub application and I see the same behavior as above, comments doesn't hide. I don't see any errors in the logs. If you need more information, don't hesitate to ask. We especially have plans on several comments. We are running Atlantis |
We just switched to using app authentication and are also seeing this error. Previously (yesterday) we were using token authentication and had no issues with this setting. |
This problem started when i switched from token to GH app. I have gh-app-slug configured however it does not hid previous plan. Just upgraded to Atlantis 0.17.0 in docker running TF .15.3 |
Here is the same, after we switched from token to GH app. Our previous comments doesn't come to hide. We run Atlantis 0.16.0 and TF .12.x |
Is there any updates on the problem where we can hide previous plan comments using github app rather then token. |
Ok so I did some code spelunking and I think I figured out what the problem is. So first of all this line (
Then when you look at the comments payload the login field as referenced here ( atlantis/server/events/vcs/github_client.go Line 196 in 1637171
has the following value
My APP was named |
For me, Hope this helps someone. |
Hello, Thanks you @chriskuchin and @davidji99, your solution is working. As pointed out by @davidji99, it is necessary to set |
Still, having an issue with this even when setting |
It is very confusing and counter intuitive, but if you app is called Hope this makes sense. |
@kpocius Thanks it now works for me this was the issue. |
@jamengual Should we keep this open until atlantis can support non lowercased github app names? Or at the very least, document this limitation? |
--hide-prev-plan-comments
flag fails if using Github App with uppercased or space chars
--hide-prev-plan-comments
flag fails if using Github App with uppercased or space chars--hide-prev-plan-comments
flag fails if using Github App name with uppercased or space chars
PRs are welcome. |
This still doesn't seem to work for me using a GitHub app and Atlantis v0.22.3. |
Ah I see, I needed to set |
Problem
I have
ATLANTIS_HIDE_PREV_PLAN_COMMENTS=true
and running 0.15.0 as a github app in ECS Fargate. I run plan manually in my repo using the following.When I run that multiple times in the same PR, it does not hide my previous plan comments.
Configuration
I have the following env vars setup in my module.
and my server atlantis.yaml is
Logs
Related
Current workaround
Thanks to comments below, the current workaround seems to be
GH User: <gh user>
ATLANTIS_GH_APP_SLUG
env to the name of the atlantis appTo resolve this in a PR
ATLANTIS_GH_APP_SLUG
should not be neededThe text was updated successfully, but these errors were encountered: