This repository has been archived by the owner on Apr 13, 2023. It is now read-only.
feat: implement multi-tenancy and group export #421
Merged
Conversation
This file contains 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
* chore: script generating patient compartment search params * feat: update Glue script for group export * Upload patient compartment jsons to S3
|
'This PR exceeds the recommended size of 1000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size.’ |
Bingjiling
reviewed
Aug 24, 2021
Bingjiling
reviewed
Aug 24, 2021
Bingjiling
reviewed
Aug 24, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 is it. This is the final merge of the
feat-smart-multitenancybranch into mainlineMost changes have been already reviewed before in separate PRs. Since this is a separate branch from
mainlinethefeat-multitenancybranch couldn't be merged as is. The commits were cherry picked and a few of them required very minor modifcations to "fit" in thesmart-developbranch.All integ tests passed on a test branch: https://github.com/awslabs/fhir-works-on-aws-deployment/actions/runs/1161939792 (except for the last merge job that was expected to fail)
You may want to focus on reviewing the last few commits after chore: upgrade dependencies: 62e7505.
Checklist:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.