NRL-1948 use new permission model#1153
Conversation
…exclude beefy tests closer to E2Es
…r client-details are missing. Move proxy code into here to grab ods code from other existing end-user-org header and expects app id to arrive in a new header nrl-app-id
…ve this a lil test mayeb in dev bucket??
|
|
🚀 PR environment successfully deployed. |
|
🚀 PR environment successfully deployed. |
…ssions in lambda layer rather than s3 (as we agreed)
|
🚀 PR environment successfully deployed. |
|
🚀 PR environment successfully deployed. |
|
🚀 PR environment successfully deployed. |
|
|
🚀 PR environment successfully deployed. |



When a request:
nhsd-connection-metadataORnhsd-client-rp-detailsheadersNHSD-End-User-Organisation-ODSheader AND the app id in thenhsd-nrl-app-idheaderNRL will attempt to lookup pointer permissions using the new permissions model -
<producer|consumer>/<app id>/<ods>.jsonin S3There are no permissions set up here yet and it wouldn't yet do anything with our new shiny ones anyways!
This is deployed on my feature branch https://anjal-dev.api.record-locator.dev.national.nhs.uk if you'd like to have a play 🛝
No environment defaults or app-level permissions in scope yet
TODO