align the cosmosdata and cosmosmetadata interfaces #3878
Conversation
Once c23fb55 makes it to production, we can rely on the new cosmosUID being predictable based on resourceID. By doing this we're able to derive resourceID which is important elsewhere. Also eliminates cosmosUID since it is an unnessary field to store since it is always derivable.
Since we migrated all the data in int, stg, and prod, the existing fixtures no longer match. Update them all to match so we can continue testing the database layer.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Trying to prevent failed to Initialize Cosmos DB: failed to create container: POST https://127.0.0.1:8081/dbs/frontend-simulation-testing-6kw5b/colls -------------------------------------------------------------------------------- RESPONSE 409: 409 Conflict ERROR CODE: 409 Conflict from bubbling up
|
@deads2k: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
This requires the rekeying be complete and builds on #3843. It aligns our cosmosdata types under one type in preparation for adding etag support.