dbaas support for mysql,pg database #410
Open
+1,525
−364
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.
Description
New resource introduced:
exoscale_dbaas_pg_database,exoscale_dbaas_mysql_database, to represent individual databases in database services.To avoid confusion with the existing
exoscale_databaseresource, it is being deprecated. A new resource is introduced,exoscale_dbaas. The only thing that changes is the name, under the hood those resources are exactly the same, except a deprecation message for the former.(I couldn't find guidance on how to rename a resource type so I have no idea if it's possible to automate the move for users)
Checklist
(For exoscale contributors)
Testing
Acceptance tests updated