[
https://issues.apache.org/jira/browse/AIRAVATA-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18066670#comment-18066670
]
Jayanth Vennamreddy commented on AIRAVATA-3972:
-----------------------------------------------
Here is the linked PR: https://github.com/apache/airavata-custos/pull/448
> 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
> Priority: Minor
> Labels: bug, config, dev-exp
>
> 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)
