Skip to content
This repository has been archived by the owner on Apr 13, 2023. It is now read-only.

Commit

Permalink
chore(release): 2.2.0-smart (#422)
Browse files Browse the repository at this point in the history
  • Loading branch information
carvantes authored Aug 25, 2021
1 parent 5335807 commit cb823c1
Show file tree
Hide file tree
Showing 3 changed files with 17 additions and 2 deletions.
15 changes: 15 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,21 @@

All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.

## [2.2.0-smart](https://github.com/awslabs/fhir-works-on-aws-deployment/compare/v2.1.0-smart...v2.2.0-smart) (2021-08-24)


### Features

* implement multi-tenancy and group export ([#421](https://github.com/awslabs/fhir-works-on-aws-deployment/issues/421)) ([5335807](https://github.com/awslabs/fhir-works-on-aws-deployment/commit/5335807c1b295b3929b9259020b5d297c0a9ecac)), closes [#367](https://github.com/awslabs/fhir-works-on-aws-deployment/issues/367) [#382](https://github.com/awslabs/fhir-works-on-aws-deployment/issues/382) [#389](https://github.com/awslabs/fhir-works-on-aws-deployment/issues/389) [#397](https://github.com/awslabs/fhir-works-on-aws-deployment/issues/397) [#398](https://github.com/awslabs/fhir-works-on-aws-deployment/issues/398) [#400](https://github.com/awslabs/fhir-works-on-aws-deployment/issues/400) [#387](https://github.com/awslabs/fhir-works-on-aws-deployment/issues/387) [#393](https://github.com/awslabs/fhir-works-on-aws-deployment/issues/393)

Multi-tenancy allows a single `fhir-works-on-aws` stack to serve as multiple FHIR servers for different tenants.
Check out our [multi-tenancy documentation](USING_MULTI_TENANCY.md) for more details.

**NOTE:** Multi-tenancy itself is not a breaking change, you can continue to use FHIR works on single-tenant mode
by not using the `enableMultiTenancy` flag.
However, note that updating an existing (single-tenant) stack to enable multi-tenancy is a breaking change. Multi-tenant
deployments use a different data partitioning strategy that renders the old, single-tenant, data inaccessible.

## [2.1.0-smart](https://github.com/awslabs/fhir-works-on-aws-deployment/compare/v2.0.0-smart...v2.1.0-smart) (2021-08-17)


Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "fhir-works-on-aws-deployment",
"version": "2.1.0-smart",
"version": "2.2.0-smart",
"description": "FHIR Works on AWS deployment with SMART",
"stackname": "fhir-works-on-aws-deployment",
"main": "src/index.ts",
Expand Down
2 changes: 1 addition & 1 deletion serverless.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ provider:
PATIENT_PICKER_ENDPOINT: ${self:custom.patientPickerEndpoint}
EXPORT_RESULTS_BUCKET: !Ref BulkExportResultsBucket
EXPORT_RESULTS_SIGNER_ROLE_ARN: !GetAtt ExportResultsSignerRole.Arn
CUSTOM_USER_AGENT: 'AwsLabs/SO0128/2.0.0-smart'
CUSTOM_USER_AGENT: 'AwsLabs/SO0128/2.2.0-smart'
VALIDATOR_LAMBDA_ALIAS:
!If
- isUsingHapiValidator
Expand Down

0 comments on commit cb823c1

Please sign in to comment.