Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

updating provisioning flags #823

Merged
merged 8 commits into from
Mar 27, 2020
Merged

updating provisioning flags #823

merged 8 commits into from
Mar 27, 2020

Conversation

jpflueger
Copy link
Contributor

@jpflueger jpflueger commented Mar 25, 2020

Closes #704

What this PR does / why we need it:
This sets the provisioning flag to false when Azure SQL resources haven't started provisioning yet due to other errors. We need this so the provisioning metric is more accurate.

Special notes for your reviewer:
Test Cases:

  1. Deploy a SQL Server database without a server and provisioning timer should not start until the server is created.
  2. Deploy a SQL Server database with an unrecoverable CreateOrUpdate error.
  3. Deploy a SQL Server VNet rule.

How does this PR make you feel:
gif

If applicable:

  • this PR contains documentation
  • this PR contains tests

Copy link
Contributor

@WilliamMortlMicrosoft WilliamMortlMicrosoft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add

instance.Status.Provisioning = false

above line 107 in the the 404 block... this block catches waiting for the underlying SQL server to provision

@jpflueger
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jpflueger jpflueger merged commit 19155b1 into Azure:master Mar 27, 2020
@jpflueger jpflueger deleted the asql-provisioning branch March 27, 2020 17:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update the AzureSQL operators to set Provisioning -> False
3 participants