Matthew Christopher
Matthew Christopher
Also see #1147, which discusses some of the flaws and risks (possible SQL injection) to the way database users were implemented in ASOv1. We should strive to avoid that in...
This is related to #1238 as well
@theunrepentantgeek - I think we did. It was removed in this PR: #2409. Specifically [here](https://github.com/Azure/azure-service-operator/pull/2409/files#diff-5794927accddb9621b12855f68facb91046f58a24fbb12fbcd0961585748eb8dR245) Although in retrospect we probably shouldn't have removed it from the `_Status` types. Do you...
@tomkerkhove - Agree that this would be cool, at least for a small subset of resources where it makes sense (there are lots where it doesn't). We're currently focusing on...
Not much different than above. We've got an alpha out for ASOv2 (based on code generation) today, but there's still a good amount of work to be done there before...
We still think this is interesting but haven't had a chance to figure out exactly what it would look like generically across resources.
Also note that we can increase our CI timeout, the limit we have was set by us I think
Specifically with `CreateMode` there's some awkward tension between goal-seeking to the customers desired state and the reality that KeyVault will fail creates if a KeyVault of the same name was...
We do support KeyVault, and this is an issue for the KeyVault resource itself as if they also have purge protection enabled on the entire vault. It causes us issues...