You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a Doppler developer, I want models designed so that AWS isn't the only first-class cloud provider so that later I can support Azure, GCP, etc.
Acceptance Criteria
Verify that database tables have been migrated to new scheme.
Verify that HTTP APIs have been updated to reflect flexibility in cloud types.
Verify that creating an account requires a "cloud provider" identifier as an input.
Verify that the returned account JSON includes the cloud provider in each instance
Verify that CLI commands have been updated to reflect flexibility in cloud types.
Tech assumptions
We probably want some parent-child class relationship for our models. This could include all of the ones defined so far.
Some "cloud provider" ID/value should be included in the account creation, but everything else going forward can continue to just use the IDs that reference back to other models.
The text was updated successfully, but these errors were encountered:
As a Doppler developer, I want models designed so that AWS isn't the only first-class cloud provider so that later I can support Azure, GCP, etc.
Acceptance Criteria
Verify that CLI commands have been updated to reflect flexibility in cloud types.Tech assumptions
The text was updated successfully, but these errors were encountered: