Fix to apply custom region for microceph (S3 and Swift) endpoints#518
Merged
Conversation
suvidyam29
force-pushed
the
fix/microceph_region
branch
from
June 16, 2025 13:28
8534124 to
c97ef47
Compare
gboutry
requested changes
Jun 16, 2025
gboutry
left a comment
gboutry
left a comment
Collaborator
There was a problem hiding this comment.
hey, thanks for the PR, this will help!
suvidyam29
force-pushed
the
fix/microceph_region
branch
from
June 16, 2025 18:49
62e6328 to
aa771a6
Compare
Collaborator
|
@suvidyam29 Can you sign the commits |
…port local snap deployment
Author
Signed commits. |
hemanthnakkina
approved these changes
Jun 17, 2025
hemanthnakkina
left a comment
hemanthnakkina
left a comment
Collaborator
There was a problem hiding this comment.
Thanks for the contribution!
gboutry
approved these changes
Jun 17, 2025
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
3 participants
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.
This PR fixes a bug (https://bugs.launchpad.net/snap-openstack/+bug/2109812) where custom region names provided via the manifest file were not reflected in the S3 and Swift service endpoints, which defaulted to "RegionOne".
What was changed?