Current behavior - When a state-migrator job is run before creating a scipian workspace, the terraform workspace created with state-migration will not sync with scipian workspace object thereby producing a Workspace already exists error. When a state-migrator job is run after creating a scipian workspace object, the dynamodb lock value associated with the s3 file path goes out of sync thereby producing the below error while creating a scipian run object:
Error: Error loading state: state data in S3 does not have the expected content. This may be caused by unusually long delays in S3 processing a previous state update. Please wait for a minute or two and try again. If this problem persists, and neither S3 nor DynamoDB are experiencing an outage, you may need to manually verify the remote state and update the Digest value stored in the DynamoDB table to the following value:
The existing behavior should be changed to resolve the scipian workspace/dynamodb sync issue
Current behavior - When a state-migrator job is run before creating a scipian workspace, the terraform workspace created with state-migration will not sync with scipian workspace object thereby producing a
Workspace already existserror. When a state-migrator job is run after creating a scipian workspace object, the dynamodb lock value associated with the s3 file path goes out of sync thereby producing the below error while creating a scipian run object:Error: Error loading state: state data in S3 does not have the expected content. This may be caused by unusually long delays in S3 processing a previous state update. Please wait for a minute or two and try again. If this problem persists, and neither S3 nor DynamoDB are experiencing an outage, you may need to manually verify the remote state and update the Digest value stored in the DynamoDB table to the following value:The existing behavior should be changed to resolve the scipian workspace/dynamodb sync issue