GCP Secrets Manager and AWS secret environment variable refactoring, possible impacts ? #2
Comments
Benvii
changed the title
sacquatella
added a commit
that referenced
this issue
Feb 3, 2025
- Add secret parameters in configmap
vsct-jburet
pushed a commit
that referenced
this issue
Feb 13, 2025
* upgrade to tock 24.9.4 * update readme * solve issue link to bad authConfigfMap typo * clean * Set a default value for vectorstore provider If no value genai_orchestrator doesn't start * Upgrade to version 24.9.4 Add tock_web_connector_extra_headers params in bot_api configmap * Solve #2 Secrets Manager - Add secret parameters in configmap * use null value vs "null" as default value for secret manager
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Based on this design several changes in environment variable may have impacts on these helm charts (I'm not 100% sure as this helm charts doesn't rely on cloud services).
theopenconversationkit/tock#1697
I'm creating this ticket so that someone can read the merged design and determine if there are impacts.
The text was updated successfully, but these errors were encountered: