This repository has been archived by the owner on Apr 13, 2023. It is now read-only.
feat!: add support for multi-tenancy and group export #116
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
BREAKING CHANGE: System export will only include resources based on what scopes you provided(SMART) or what resources align with said group(RBAC)
Bingjiling
suggested changes
Aug 13, 2021
carvantes
changed the title
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 the final merge of the feat-multitenancy branch into mainline
All changes have been reviewed before in separate PRs (except the last
chore: update fhir-works-on-aws-interface version, but that's just bumping npm dependencies)By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.