-
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
Issue restricting what workflows each repo has access to #1358
Comments
The intent of the feature is exactly as you are interpreting it. The idea was to allow projects to specify a couple of server side defined pre-approved workflows. I need to look into it a little bit, but you're correct, this needs to work without |
yes, this is wrong: |
Just to give you a quick update! Work got on the way, but I have a fix ready, I just need to test it a bit to make sure it behaves as expected. I also added a new test to verify that it verifies correctly without |
Awesome, thanks @netguino for the speedy response on this. Much appreciated 👍 |
Version:
0.16.0
Hi, firstly thanks for an awesome project.
I'm interested in implementing the use case detailed here. Namely, I'd like to be able to define all of my custom workflows server-side and then restrict which of these workflows are available to repos (using the
allowed_workflows
key).This is my
atlantis.yaml
config:And the corresponding server-side config (I'm using Jsonnet - the following object is eventually rendered, converted to a string and exposed as the
ATLANTIS_REPO_CONFIG_JSON
env var in theStatefulSet
):So, based on my understanding of the doco this should satisfy my use case. However, I'm seeing the following error in the logs:
I had a bit of a dig through the code and found what I believe is the issue. If I add the following item to my server-side config, I no longer encounter the problem:
However, this then permits a user to redefine in
atlantis.yaml
the definition of any workflow defined inallowed_workflows
(e.g.terragrunt
in this case) which seems to violate the purpose ofallowed_workflows
.Would appreciate any feedback re this.
The text was updated successfully, but these errors were encountered: