Trez/rinoa-docker
4
0
Fork 0
Code Issues 1 Pull Requests 8 Actions Activity

Ansible DRY fixes for Vault lookups.
Gitea Branch PR & Ansible Deployment / Check and Create PR (push) Failing after 3m6s
Details
Gitea Branch PR & Ansible Deployment / Docker Compose & Ansible Lints (push) Has been skipped
Details
Gitea Branch PR & Ansible Deployment / PR Merge (push) Failing after 9m4s
Details
Gitea Branch PR & Ansible Deployment / Ansible Configs & Docker Compose Deployment (push) Has been skipped
Details

Browse Source
This commit is contained in:
Trez.One
2025-05-20 09:06:49 -04:00
parent c804bb6dab
commit 6b37ad8ea4
37 changed files with 118 additions and 112 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ansible/app-configs/grafana_tempo_tempo.yaml.j2
+2 -2
View File
@@ -46,8 +46,8 @@ storage:
s3:
bucket: tempo # how to store data in s3
endpoint: minio:9000
access_key: {{ lookup('community.hashi_vault.vault_kv2_get', 'env', engine_mount_point='rinoa-docker', url=vault_addr, token=vault_token_cleaned)['secret']['MINIO_TEMPO_STORAGE_ACCESS_KEY'] }}
secret_key: {{ lookup('community.hashi_vault.vault_kv2_get', 'env', engine_mount_point='rinoa-docker', url=vault_addr, token=vault_token_cleaned)['secret']['MINIO_TEMPO_STORAGE_SECRET_KEY'] }}
access_key: {{ vault_secrets['MINIO_TEMPO_STORAGE_ACCESS_KEY'] }}
secret_key: {{ vault_secrets['MINIO_TEMPO_STORAGE_SECRET_KEY'] }}
insecure: true
usage_report: