[DND-1416] Add optional azureblob regions (jclouds.regions) for bucket creation - #23
Merged
Merged
Conversation
… creation
The azureblob-sdk provider on real Azure needs jclouds.regions to create
buckets; without it `aws s3 mb` fails with InvalidLocationConstraint ("no
jclouds.regions configured for provider azureblob-sdk") — GH issue #15.
Add an optional config.backends.azureblob.regions value, emitted as
jclouds.regions= in the azureblob backend properties when set (omitted when
empty, so Azurite and other backends are unaffected).
This completes the chart mechanism for DND-1416 item 2. Items 1 (endpoint
typo) and 3 (default-endpoint guard) already landed via PR #22. The endpoint
fix + azureblob-sdk provider are confirmed against Azurite; the real-Azure
bucket-create fix (correct default region) still needs validation against a
live Azure backend.
No Chart.yaml version bump (deferred, handled separately), so verify-version
fails by design for now.
Verified on kind: azureblob-sdk + jclouds.regions round-trips against Azurite;
helm lint + kubeconform (all test-values) clean; regions omitted when empty.
📝 README.md PreviewThe following changes to Click to expand diffdiff --git a/README.md b/README.md
index dfcde1c..b95b0fe 100644
--- a/README.md
+++ b/README.md
@@ -140,6 +140,12 @@ The following section lists the configurable parameters of the s3proxy chart and
<td><code>string</code></td>
<td><code>"azureblob"</code></td>
</tr>
+ <tr>
+ <td><code>config.backends.azureblob.regions</code></td>
+ <td>jclouds region(s) for the backend, emitted as <code>jclouds.regions=</code>. The azureblob-sdk provider requires this on real Azure to create buckets (without it <code>aws s3 mb</code> fails with InvalidLocationConstraint / "no jclouds.regions configured"). Comma-separated for multiple. Not needed against Azurite. Leave empty to omit.</td>
+ <td><code>string</code></td>
+ <td><code>""</code></td>
+ </tr>
<tr>
<td><code>config.backends.azureblob.sasToken</code></td>
<td>SAS token configuration</td>
|
📊 Helm Render Diff SummaryChart
🎉 No changes detected in any of the tested configurations! |
This was referenced Jul 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Completes DND-1416 item 2 (GH issue #15). The
azureblob-sdkprovider on real Azure needsjclouds.regionsto create buckets; without itaws s3 mbfails withInvalidLocationConstraint("no jclouds.regions configured for provider azureblob-sdk"). The chart had no way to set it.Items 1 (endpoint property typo) and 3 (default-endpoint guard) already landed via PR #22.
Change
config.backends.azureblob.regions. When set, the azureblob backend properties emitjclouds.regions=<value>(comma-separated for multiple). When empty (the default), nothing is emitted, so Azurite and every other backend are unaffected.Verification
regionsset emitsjclouds.regions=; empty omits it.helm lintandkubeconform -strict(k8s 1.29, all test-values): clean.azureblob-sdk+jclouds.regionsstill round-trips create/put/get against Azurite (the knob wires through without breaking the working path).Not covered here
InvalidLocationConstraintfix (and the correct default region) needs a live Azure backend, which isn't available in CI or the agentro environment. This PR provides the knob and confirms it renders and wires through against Azurite; closing issue cannot create bucket #15 should wait on a real-Azureaws s3 mbcheck withregionsset.providerstaysazureblob(unchanged); whether to makeazureblob-sdkthe default is deferred.Notes
Chart.yamlversion bump (deferred, handled separately with the other accumulated chart changes), soverify-versionfails by design for now.README.md; onlyvalues.yaml(which drives the values table) is edited here.