Issues
- 2
[FR] Require a 'secret' in order to create existing binding to Azure SQL failover group
#6 opened by claassen - 4
- 3
- 2
- 1
[FR]
#555 opened by ElsaChelala - 5
- 3
- 3
- 3
- 8
Upgrading within the same plan is now fixed in terms of actually updating both the primary and secondary DB instance, but still seeing issues upgrading from Basic to Standard tier with the latest release (1.0.0-rc39):
#47 opened by blgm - 6
Cloud Service Broker (0.2.7 / 1.0.0-rc.40) failed to subsume db with failover group with db storage size near the capacity
#53 opened by kelvin-j-li - 9
[BUG] Subsume instance creation failure causes underlying target resource to be deleted
#10 opened by claassen - 18
- 3
- 1
- 4
[BUG] Azure SQL FOG subsume fails with "Must provide values for all import parameters: azure_primary_db_id, azure_secondary_db_id, azure_fog_id" even though provided
#7 opened by claassen - 0
[BUG] Creating Azure SQL Failover group sometimes fails due to databases already being in replication relation
#8 opened by claassen - 3
[BUG] App binding credentials do not work after performing failover of Azure SQL DB
#4 opened by claassen - 6
[DOCS] Handling multiple azure_subscription_id, azure_client_id and azure_client_secret with Azure Brokerpack
#2 opened by drebake