mikyll opened a new issue, #13233: URL: https://github.com/apache/apisix/issues/13233
### Description Similar to #13132 I'd like to avoid writing the api key in plain text in the plugin configuration and use a secret reference (Secret Manager or environment variable, see [APISIX Docs | Secret](https://apisix.apache.org/docs/apisix/terminology/secret/)). Current situation: ```yaml routes: - id: ai-rag-azure uri: /ai/rag plugins: ai-rag: embeddings_provider: azure_openai: endpoint: "https://ai-plugin-developer.openai.azure.com/openai/deployments/text-embedding-3-large/embeddings?api-version=2023-05-15"; api_key: "myopenaiapikey" vector_search_provider: azure_ai_search: endpoint: "https://ai-plugin-developer.search.windows.net/indexes/vectest/docs/search?api-version=2024-07-01 api_key: "myazuresearchapikey" ai-proxy: # ... ``` Feature request: ```yaml routes: - id: ai-rag-azure uri: /ai/rag plugins: ai-rag: embeddings_provider: azure_openai: endpoint: "https://ai-plugin-developer.openai.azure.com/openai/deployments/text-embedding-3-large/embeddings?api-version=2023-05-15"; api_key: "$ENV://AZURE_OPENAI_APIKEY" vector_search_provider: azure_ai_search: endpoint: "https://ai-plugin-developer.search.windows.net/indexes/vectest/docs/search?api-version=2024-07-01 api_key: "$ENV://AZURE_AI_SEARCH_APIKEY" ai-proxy: # ... ``` ## Implementation Just call `apisix.secret.fetch_secrets()` on the embeddings and vector_search configuration tables, to resolve secret references if present. I can submit a PR to implement this feature 🙂 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
