oncall-engine/helm/oncall/tests/service_account_test.yaml
Alexander Cherepanov d3247447ef
Fix usage of extra envs as map in Helm chart (#2146)
# What this PR does


1. Fixes setting extra envs using:
```yaml
env:
  proxy: http://example.com
  SOME_VAR: some-value
```
It had failed if postgresql setting enabled and in `job-migrate`

2. Fixes an issue if custom database and username set for internal
mariadb, `MYSQL_` envs did not use them
```yaml
mariadb:
  auth:
     database: grafana_oncall
     username: grafana_oncall
```

3. Added `imagePullSecrets: []` to values.yaml. It used in helm chart,
but does not present in the values.yaml
4. More unit tests

## Which issue(s) this PR fixes

## Checklist

- [x] Unit, integration, and e2e (if applicable) tests updated
- [ ] Documentation added (or `pr:no public docs` PR label added if not
required)
- [x] `CHANGELOG.md` updated (or `pr:no changelog` PR label added if not
required)

Co-authored-by: Ildar Iskhakov <Ildar.iskhakov@grafana.com>
2023-06-12 03:34:36 +00:00

44 lines
1.1 KiB
YAML

suite: test service account
templates:
- serviceaccount.yaml
release:
name: oncall
tests:
- it: serviceAccount.create=true -> should create serviceAccount (default)
asserts:
- containsDocument:
kind: ServiceAccount
apiVersion: v1
name: oncall
- notExists:
path: metadata.annotations
- isSubset:
path: metadata.labels
content:
app.kubernetes.io/instance: oncall
app.kubernetes.io/name: oncall
- it: serviceAccount.create=false -> should not create serviceAccount
set:
serviceAccount.create: false
asserts:
- hasDocuments:
count: 0
- it: serviceAccount.name=custom -> should create custom serviceAccount
set:
serviceAccount.name: custom
asserts:
- equal:
path: metadata.name
value: custom
- it: serviceAccount.annotations -> should add annotations to serviceAccount
set:
serviceAccount.annotations:
some-annotation: some-value
asserts:
- isSubset:
path: metadata.annotations
content:
some-annotation: some-value