Skip to content

Environments

Michael J Burling edited this page May 13, 2023 · 8 revisions

Environments

Established Environments

Established environments support BFD's path-to-production and include test, prod-sbx, and prod.

test

PHI/PII Reliability Access
No Non-Production Internal

Historically, the test environment has been used as a common integration testing environment. The process for deploying changes to test supports on-demand deployments of individual contributors' feature branches and pull requests. This environment is also used in determining production-readiness of a given change set. Generally, software changes that are based off the trunk or master branch of the beneficiary-fhir-data repository can be promoted to a production deployment after the changes yield a successful deployment in test.

As of mid 2022, the test environment was expanded to include additional resources to be more production-like, including both resource scaling-out and scaling-up to the RDS cluster and BFD FHIR API Server AutoScaling Group. Along with more production-like resources, BFD has also loaded an additional 10 million synthetic beneficiaries and associated claims data to facilitate performance and load testing. As a result, test can also be used as a performance testing environment.

prod-sbx

PHI/PII Reliability Access
No Production External

prod

PHI/PII Reliability Access
Yes Production Internal

Ephemeral Environments

Constraints

Clone this wiki locally