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.
Closes #231
What this PR does / why we need it:
Note: Initially a WIP - Waiting for some firewall rule code to get merged before doing a rename on those files.
Renames SqlServer, SqlDatabase, SqlFirewallRule, and SqlAction (rolling credentials) to AzureSqlServer, AzureSqlDatabase, AzureSqlFirewallRule, and AzureSqlAction, respectively. Resolves ambiguity in the type of SQL services being implemented, and makes room for other future database implementations such as PostgresSQL or MySQL, etc.
Special notes for your reviewer:
Run operator and check to make sure that an AzureSQL server, database, and firewall rule can still be created successfully and show up in the portal. Get the DB password from the k8s secret, base64 decode, then use it to log into the database to test. Run the AzureSqlAction to roll credentials using the operator. Get the new password from the k8s secret, base64 decode, then test to make sure the new password can be used to log into the database.
If applicable: