fix issue with CloudWatch after state reset #12755
Merged
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.
Motivation
This PR fixes an issue that occurs when the CW Provider is restared and the user tries to write some metrics into the service with the "clean" state.
The cause of this issue is that the reset operation removes the directory
/tmp/localstack/state/cloudwatch
and the DB files inside it. After the reset operation, the provider doesn't start a new DB file. So any operation that comes after failes.Changes
Testing (Not)