This message was deleted.
# atlantis-community
s
This message was deleted.
p
I’m pretty sure we renamed this to
allowlist
@Dylan Page do you know?
d
I’ll take a look in a second
m
I have the variable orgWhitelist set, it's there in the latest example as well
p
are you updating the chart and using an old version of Atlantis by any chance?
m
I'll try with the latest image
using 0.20.0
d
I 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
I'll keep you updated, thank you
p
the 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
@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 ATLANTIS
m
This 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
there 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
using the personal access token instead of the password made it work
p
and you passed that to which flag?
m
I 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