Skip to content

Development: Use new openai azure keys#64

Merged
bensofficial merged 2 commits intomainfrom
feat/use-new-openai-api-keys
Apr 8, 2026
Merged

Development: Use new openai azure keys#64
bensofficial merged 2 commits intomainfrom
feat/use-new-openai-api-keys

Conversation

@bensofficial
Copy link
Copy Markdown
Member

@bensofficial bensofficial commented Apr 7, 2026

Summary by CodeRabbit

  • Chores
    • Switched the Azure OpenAI credential reference to the production key in configuration to strengthen secret handling and key management practices.

@bensofficial bensofficial self-assigned this Apr 7, 2026
@bensofficial bensofficial requested a review from a team as a code owner April 7, 2026 10:11
@bensofficial bensofficial changed the title Use new openai azure keys Development: Use new openai azure keys Apr 7, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 7, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8fda9ec3-566c-4232-b12a-e3c40a7ffeaf

📥 Commits

Reviewing files that changed from the base of the PR and between 3fa86f9 and 3ace81a.

📒 Files selected for processing (1)
  • group_vars/artemis_prod_like_common.yml

📝 Walkthrough

Walkthrough

Changed the Vault lookup for spring_ai.azure_openai.api_key in a production-like group vars file to use the azure_openai_api_key_prod key at kv/data/artemis/common/hyperion instead of the previous key.

Changes

Cohort / File(s) Summary
Configuration Update
group_vars/artemis_prod_like_common.yml
Replaced Vault key lookup for spring_ai.azure_openai.api_key: now reads azure_openai_api_key_prod from kv/data/artemis/common/hyperion (endpoint, deployment_name, temperature unchanged).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A vault key danced from old to new,
Quiet hops to a hyperion view,
Prod path beckoned, credentials align,
Azure whispers neatly on a single line,
I nibble configs — all set, all fine.

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main change: updating Azure OpenAI API key configuration to use new keys from Vault.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/use-new-openai-api-keys

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@bensofficial bensofficial merged commit d9f1bb9 into main Apr 8, 2026
2 checks passed
@bensofficial bensofficial deleted the feat/use-new-openai-api-keys branch April 8, 2026 13:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant