ASRE-550: Fix WORKLOAD_API_BEARER_TOKEN issue #376
+3
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
This change updates the WORKLOAD_API_BEARER_TOKEN to use a dynamic value by referencing bearerToken in the workload-api and workload-api-server sections from the Helm values file.
How
This modification uses Helm's index function to dynamically fetch the bearerToken values from .Values.workload-api and .Values.workload-api-server, ensuring that the correct token is used for authentication. The tokens are now quoted properly for use in Kubernetes configurations.
Before:
WORKLOAD_API_BEARER_TOKEN: {{ index ".Values.workload-api.bearerToken" | quote }}
After:
WORKLOAD_API_BEARER_TOKEN: {{ index .Values "workload-api-server" "bearerToken" | quote }}
Can this PR be safely reverted and rolled back?