Skip to content

[HYRAX-1732] Add SignedUrlCache and cache contents of s3credential endpoints#1183

Draft
hannahilea wants to merge 108 commits intomasterfrom
hr/HYRAX-1732-TEA-party-3
Draft

[HYRAX-1732] Add SignedUrlCache and cache contents of s3credential endpoints#1183
hannahilea wants to merge 108 commits intomasterfrom
hr/HYRAX-1732-TEA-party-3

Conversation

@hannahilea
Copy link
Copy Markdown
Contributor

@hannahilea hannahilea commented Oct 29, 2025

Description

  • Cache contents of s3credential endpoint urls
  • Set up and test SignedUrlCache class, as alternative to EffectiveUrlCache

This is a big step toward HYRAX-1732, but does not yet implement the signing itself---end-users will still receive effective urls created via service chaining. This PR adds the main plumbing to set us up for self-signing in the next PR. Includes the self-signing; will close HYRAX-1732 when tested/merged.

Tasks

  • Ticket exists and is linked in title
  • Tests added/updated
  • Dead code removed
  • No TODOs added (well, one! but intentionally b/c that HAS to happen next)
  • Linking works on all Travis builds
  • End-to-end tests added (and run on travis)
  • Tested on SIT

@hannahilea hannahilea marked this pull request as ready for review October 31, 2025 20:08
@hannahilea
Copy link
Copy Markdown
Contributor Author

Opening this for review but it should NOT be merged until the next PR is ready to go (and tested on SIT)---don't want to add unnecessary steps to the service chain until it actually buys us the win!

@hannahilea
Copy link
Copy Markdown
Contributor Author

There is a fair amount of code added; probably the easiest way to understand it is to start by reading through the test page, since that is fairly comprehensive (I think).

@hannahilea hannahilea marked this pull request as draft March 13, 2026 21:10
@hannahilea
Copy link
Copy Markdown
Contributor Author

Ran build on SIT, request failed as a 403.

We (successfully?) "request s3 credentials from TEA" After that, we fail with a "URL is not on the Allowed Hosts list and is not a known trusted URL" error. The url does have signing params in it, however, so I suspect that this is a problem with our initial set-up some how.

Next step: see if we can recreate this locally.

@ndp-opendap
Copy link
Copy Markdown
Contributor

ndp-opendap commented Mar 14, 2026

See my DM in Slack

@sonarqubecloud
Copy link
Copy Markdown

@sonarqubecloud
Copy link
Copy Markdown

@sonarqubecloud
Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants