SSWConsulting / SSWConsulting/SSW.Walrus
Move the Azure infrastructure to the SSW Azure subscription
Open
@edkranz is already working on this.
Since Jul 13, 2026.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 6h 21m
- Merged PRs (30d)
- 1
Description
Problem
SSW.Walrus is currently deployed to a personal/staging Azure subscription (rg-walrus-staging, acrwalrusstaging, func-walrus-staging, sawalrusstaging / sawalrusstagingweb). It needs to run on SSW-owned Azure so it's not tied to a personal account.
Goal
Deploy the whole Walrus stack under the SSW Azure subscription/tenant with SSW-owned identity and secrets.
Acceptance criteria
- Infra (
infra/main.bicep) deployed into an SSW resource group under the SSW subscription. - GitHub OIDC federated credential re-created against the SSW tenant; repo
AZURE_CLIENT_ID/AZURE_TENANT_ID/AZURE_SUBSCRIPTION_IDvars updated soazure-deploy.ymldeploys to SSW. - Key Vault secrets re-provisioned in the SSW vault (
anthropic-oauth-token,elevenlabs-api-key— see linked issue). - Container App Job env (
DASHBOARD_STORAGE_ACCOUNT,DASHBOARD_BASE_URL,LOGBOOK_VOICE) updated for the SSW resources. - A full run (ingest → dashboard → deploy → email) verified end-to-end on SSW infra.
- Personal-subscription resources decommissioned once cutover is confirmed.
Notes
- Blocks / relates to the Power Automate move (connections point at the SSW storage account) and the ElevenLabs key.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.