#atlantis (2023-04)
| Discuss the Atlantis (<http://runatlantis.io | runatlantis.io>) |
**Archive: ** https://archive.sweetops.com/atlantis/
2023-04-10
v0.23.4 What’s Changed chore(changelog): Add v0.23.3 by @jamengual in <a class=”issue-link js-issue-link” data-error-text=”Failed to load title” data-id=”1633026016” data-permission-text=”Title is private” data-url=”https://github.com/runatlantis/atlantis/issues/3249“…
2023-04-17
v0.23.5 What’s Changed fix(changelog): no need to update changelog by @nitrocode in <a class=”issue-link js-issue-link” data-error-text=”Failed to load title” data-id=”1661493786” data-permission-text=”Title is private”…
v0.23.5 What’s Changed fix(changelog): no need to update changelog by @nitrocode in <a class=”issue-link js-issue-link” data-error-text=”Failed to load title” data-id=”1661493786” data-permission-text=”Title is private”…
2023-04-20
I need help with server side repo config please. I installed with helm/kustomize so im working with a values.yaml and then an atlantis.yaml file to set up my repos. I get this error if i try to run plan:
repo config not allowed to set 'apply_requirements' key: server-side config needs 'allowed_overrides: [apply_requirements]
In my values.yaml file I have the following:
## Use Server Side Repo Config,
## ref: <https://www.runatlantis.io/docs/server-side-repo-config.html>
## Example default configuration
repoConfig: |
# ---
repos:
id: /.*/
workflow: default
allowed_overrides: [apply_requirements]
allow_custom_workflows: false
Then in my Atlantis.yaml file I have this:
version: 3
projects:
&template
dir: template
autoplan:
enabled: false
apply_requirements: [mergeable, approved, undiverged]
<<: *template
dir: service/thing1
workspace: dev
<<: *template
dir: service/thing1
workspace: stage
<<: *template
dir: service/thing1
workspace: prod
What am I missing here?
Figured it out…stupid yaml spacing…
repoConfig: |
---
repos:
- id: /.*/
workflow: default
allowed_overrides: [apply_requirements]
apply_requirements: [approved]
2023-04-24
2023-04-27
Does anyone have an example of how you pull aws secrets into your values.yaml file if you have deployed with helm to eks? This is all I can find and theres nothing in the docs…not helpful at all. Im wanting to have my values file pull the github webtoken and secret from my AWS Secrets.
# To reference an already existing Secret object with AWS credentials
# awsSecretName: 'mysecretwithawscreds'
I will say, you might get more answers in the Atlantis slack
OK…Ill ask you there too.
no me because I do not use K8s but other people do
This was mentioned in this weeks recent office hours: https://github.com/helmfile/vals
It looks like a tool that would help for your use case.