Matthew Christopher
Matthew Christopher
This is a place to catalog issues we've noticed with upstream Swagger/JSON specs. Once we've got a large list we can submit PRs or Issues to the corresponding specs. Note...
**Items:** 1. `PostgreSQLServer` should have a `PostgreSQLServerAdministrator` subresource, allowing customers to delegate user creation permissions to the managed identity ASO is running as. (see `MySQLServerAdminstrator` for an example of this...
As originally requested in #1396, @EdYa was looking for a way to allow another namespace access to the secret created by a `PostgreSQLUser`. > I could imagine that annotation support...
**Describe the current behavior** The resource manager schema implies that all resources implement `resourceBase`, which has `tags` and a few other properties. This is not correct though, there are multiple...
@matucker-msft was asking me about this for an incubation project he was working on.
We should support MySQL, PostgreSQL and AzureSQL users like we do in ASOv1. This will require designing and implementing manual reconcilers for the first time in ASOv2, so we may...
The spec for this resource is derived from [this](https://schema.management.azure.com/schemas/2018-03-01/Microsoft.Insights.json#/definitions/MetricAlertCriteria) and ends up looking like: ``` //Generated from: https://schema.management.azure.com/schemas/2018-03-01/Microsoft.Insights.json#/definitions/MetricAlertCriteria type MetricAlertCriteria struct { //MetricAlertMultipleResourceMultipleMetric: Mutually exclusive with all other //properties MetricAlertMultipleResourceMultipleMetric...
Support creation of Azure Functions in ASOv2. Functions is actually a `Microsoft.Web/sites` of type `functionapp` (see [ARM template](https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-first-function-resource-manager?tabs=visual-studio-code%2Cazure-cli)), which requires the following additional resources as well: - Microsoft.Storage/storageAccounts - Microsoft.Web/serverfarms...
Since CRDs will be in different groups, standard Kubernetes conversions won't work, but we don't want customers to have to manually mirror all of their resources. This probably will be...
In a vein similar to the [alternative multitenancy approach](https://github.com/Azure/azure-service-operator/blob/main/docs/v1/design/multitenancy.md#alternatives) we have discussed before, we've had users ask for the ability to manage multiple subscriptions in a single namespace. One way...