-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(mtls): trust store and mtls #1430
Conversation
Refs: #1377'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
flagging this a needs review, for bookkeeping due to this: #1430 (comment)
Refs: #1442
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added some Qs - also once this PR is approved I'd suggest just creating the prod resources as well, rather than waiting for go-live ( so we don't forget)
@@ -17,6 +17,7 @@ export const handler = Sentry.AWSLambda.wrapHandler(async (event: APIGatewayProx | |||
id: payload.id, | |||
timestamp: payload.timestamp, | |||
samlAttributes: payload.samlAttributes, | |||
patientResource: payload.patientResource, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what does this have to do with mTLS?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah nothing was just an improvement to the PD logic. Was a lingering change I just added herer
addProxyRoute("/v1/patient-discovery", buildInboundAddress(patientDiscoveryPort), apiGateway); | ||
addProxyRoute("/v1/document-query", buildInboundAddress(documentQueryPort), apiGateway); | ||
addProxyRoute("/v1/document-retrieval", buildInboundAddress(documentRetrievalPort), apiGateway); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why did you remove const apiRootV1 = api.root.addResource("v1");
in favor of putting /v1
in every URL?
why not just build there from the apiRootV1
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
APIGatewayV2 doesnt support ".root" or the type that apiRoot was (an apig.IResource). This was the only way I could figure out to from the aws docs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉 This PR is included in version 5.63.0-develop.7 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 5.64.0-develop.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 5.64.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Refs: #1377
Dependencies
Description
Testing
Release Plan