add azure blob config to chart

[olamilekan000]

change add azure blob config to chart

---

Note

Medium Risk
Changes how cloud storage credentials are injected at deploy time; Azure adopters must use Secret key accountKey or upgrades from extraEnvs/account_key can fail silently on missing credentials.

Overview
Adds first-class Azure Blob object storage to the Convoy Helm chart for server and agent (Deployment and Rollout templates), driven by storage.type: azure_blob and new storage.azure_blob.* values that map to CONVOY_STORAGE_AZURE_* environment variables.

Account keys can be set inline or via an existing Secret (storage.azure_blob.secret), with the Secret key accountKey (documented separately from S3’s secretKey). README / README.md.gotmpl add an Object Storage section with examples and an upgrade note for teams moving off extraEnvs who may still have account_key in their Secret.

S3 wiring is tightened on the server side: optional storage.s3.prefix is emitted as CONVOY_STORAGE_AWS_PREFIX, and the S3 secret reference guard matches the agent pattern (and + non-empty check). Default values.yaml and subchart values gain matching azure_blob (and agent s3.prefix) blocks; generated README values table reflects the new fields.

^{Reviewed by Cursor Bugbot for commit 6769139. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mekilis]

Before merge, run helm template with env.storage.enabled=true and env.storage.type=azure_blob, once with inline account_key and once with secret, to confirm both branches render. Env var names match the server's config.go and the type goes through the existing CONVOY_STORAGE_POLICY_TYPE, so this is just a formality.

[mekilis]

The secret must store the key as accountKey (camelCase), matching the README. Add an upgrade note: anyone who used the old extraEnvs workaround created the secret with account_key and needs to recreate it as accountKey. Note also that S3 uses secretKey here while Azure uses accountKey, so the two aren't symmetric by name.

Same applies at charts/server/templates/rollout.yaml:369, charts/agent/templates/deployment.yaml:361, and the paired line in charts/agent/templates/rollout.yaml.

[mekilis]

The sentinel keys and JWT row reordering are unrelated to Azure Blob. They're helm-docs catching up on pre-existing drift. Harmless, just noting it widens the diff.