You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "Jayanth Vennamreddy (Jira)" <ji...@apache.org> on 2026/03/19 02:12:00 UTC
[jira] [Created] (AIRAVATA-3972) Fix malformed VAULT_LOCAL_CONFIG JSON in docker-compose.yml
Jayanth Vennamreddy created AIRAVATA-3972:
---------------------------------------------
Summary: Fix malformed VAULT_LOCAL_CONFIG JSON in docker-compose.yml
Key: AIRAVATA-3972
URL: https://issues.apache.org/jira/browse/AIRAVATA-3972
Project: Airavata
Issue Type: Improvement
Components: Custos Airavata Integration
Environment: Local development environment using docker-compose
Reporter: Jayanth Vennamreddy
While reviewing the development setup, I noticed that the VAULT_LOCAL_CONFIG value in compose/docker-compose.yml contains malformed JSON.
Current configuration:
'\{"listener": [...], "default_lease_ttl": "168h", "max_lease_ttl": "720h"}, "ui": true}'
The closing brace is misplaced, causing the "ui": true property to be outside the JSON object. This results in invalid JSON and may prevent Vault from correctly enabling the UI when running the local development stack.
Proposed fix:
Move the closing brace to include the "ui" field within the JSON object:
'\{"listener": [...], "default_lease_ttl": "168h", "max_lease_ttl": "720h", "ui": true}'
Impact:
- Ensures valid JSON configuration
- Enables Vault UI correctly in local development
- Improves developer experience when running docker-compose
I can open a PR to fix this if this approach looks good.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)