Title
m
Manav Sikka
04/05/2023, 3:00 PMHi, I am upgrading the atlantis version, moving from helm chart version 3.12.11 to 4.12.2, facing issue with the pod, getting this error: Error: --repo-whitelist must be set for security purposes, I have the variable configured and can see it in the deployment as well: ATLANTIS_REPO_ALLOWLIST : <my-repo>, any idea on what could be wrong here?
p
PePe Amengual
04/05/2023, 3:55 PMI’m pretty sure we renamed this to
allowlist@Dylan Page do you know?
d
Dylan Page
04/05/2023, 4:00 PMI’ll take a look in a second
m
Manav Sikka
04/05/2023, 4:04 PMI have the variable orgWhitelist set, it's there in the latest example as well
p
PePe Amengual
04/05/2023, 4:16 PMare you updating the chart and using an old version of Atlantis by any chance?
m
Manav Sikka
04/05/2023, 4:25 PMI'll try with the latest image
using 0.20.0
d
Dylan Page
04/05/2023, 4:26 PMI think the env var in the helm chart doesn’t line up with the Atlantis flag, but I’m mobile atm
I can’t confirm 100%
m
Manav Sikka
04/05/2023, 4:27 PMI'll keep you updated, thank you
p
PePe Amengual
04/05/2023, 4:28 PMthe whitelist in all the flags was renamed like 1.5 years ago so you will have to be in a very old version to get that error
like 0.17 something
d
Dylan Page
04/05/2023, 7:23 PM@Manav Sikka The error indicates neither flags are being set: https://github.com/runatlantis/atlantis/blob/main/cmd/server.go#L878-L886
From what I can tell, everything should work fine on the latest version. Viper should autoEnv the RepoAllowlistFlag
Can you exec into the pod and make sure the environment variable is set properly?
env | grep ATLANTISm
Manav Sikka
04/11/2023, 8:42 AMThis worked with the latest image, thank you 🙂
I have another question, the communication between the atlantis pod and bitbucket dosen't seem to be working, though I am successfully able to test the connection from the webhooks, I am getting authorization exception in the atlantis pod logs, while running a plan on my bitbucket project "You are not permitted to access this resource"
my bitbucket server runs on https, and I haven't provided any cert, as it wasn't required on the old atlantis versions, as per my knowledge, has this been enforced now?
I have verified the credentials I am using, and they work fine, using them on the old atlantis deployment as well
@Dylan Page @PePe Amengual could you please support me with this as well, thank you
p
PePe Amengual
04/11/2023, 3:24 PMthere has been some changes on bitbucket code to add a few things. check the docs and merged PRs and see
you can figure out what version was the pr merge for and try downgrading to it to see if that is the issue
m
Manav Sikka
04/13/2023, 11:06 AMusing the personal access token instead of the password made it work
p
PePe Amengual
04/13/2023, 3:30 PMand you passed that to which flag?
m
Manav Sikka
04/13/2023, 3:56 PMI passed that as the vcsSecretName, which i have been using with the old version as well, but with the user password, not with the personal access token