NOJIRA: Replace cspace-maven-repo#549
Open
mikejritter wants to merge 2 commits into
Open
Conversation
Member
|
@mikejritter the new bucket won't be (shouldn't be) publicly accessible, you'll want to go through the CloudFront url: https://cspace-maven.collectionspace.org (ask @mglyrasis for details). |
Contributor
Author
|
@mark-cooper Oh thanks, I was thinking about whether or not we could create a cname for it so we wouldn't have to deal with this in the future and was just looking at cloudfront for that. Would be nice if these things were communicated with us though. |
spirosdi
approved these changes
Jul 2, 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
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.
What does this do?
Replaces cspace-maven-repo with cspace-program-production-cdn-cspace-maven
Why are we doing this? (with JIRA link)
No jira. The s3 bucket with the maven repository is changing accounts and this is the new bucket name.
How should this be tested? Do these changes have associated tests?
Rebuild cspace with this PR
Dependencies for merging? Releasing to production?
None
Has the application documentation been updated for these changes?
No
Did someone actually run this code to verify it works?
I got a 403 when trying to build so I assume the change hasn't been made yet. Once it builds successfully I'll set this as being ready.
Have any new security vulnerabilities been handled?
n/a