Changing constraints on cloud resource specifications tables to prevent extra rows #1511
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR changes the constraints on the modw_cloud.cloud_resource_specifications and modw_cloud.staging_resource_specifications tables to prevent there being more than one row for a host for a day. Previously, you could have two rows for a host on a day which would cause incorrect data and/or errors when trying to aggregate the cloud resource specifications data.
Motivation and Context
Preventing errors and incorrect data
Tests performed
Tested in docker. Both fresh install and the upgrade
Checklist: