System test upgrading an instance
- Dominant language
- Java
- Stars
- 107
- Forks
- 29
- Avg merge
- 19h 46m
- Merged PRs (30d)
- 141
Description
### User Story
As a developer of Sleeper, I want to know when something I do breaks the upgrade process, so that I can avoid releasing that change.
### Description / Background
Under epic:
- https://github.com/gchq/sleeper/issues/4235
There are a number of changes we could make that would cause CloudFormation to delete and recreate resources in AWS. For certain resources this can have a big impact on a Sleeper instance.
We'd like to test an upgrade with all optional components included, and have some automated process to warn us when resources are recreated as part of an upgrade. It could be difficult to find such a problem manually.
### Technical Notes / Implementation Details
We can system test against a specific old version, not just the most recent. We can add some data before the upgrade, and query it afterwards.
We can look for a way to confirm the CDK deployment won't recreate anything important.
If we do this in our pre-publishing repository we can take advantage of pre-published artefacts to test upgrading from a specific version.
Contributor guide
Assessment
This issue has not been assessed yet.