You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 6, 2022. It is now read-only.
You support to set tags when provisioning a new "azure-sql-12-0" or "azure-sql-12-0-dbms" service, but it is not possible to set tags for a "azure-sql-12-0-database" service .
Since the name of the database cannot be determined, tags could help to identify the database in the azure portal and via CLI.
You already set a tag "heritage : open-service-broker-azure" on every new DB, so i hope the api exist to set tags for new DBs.
This would be very helpful to manage databases requested via osba in the azure portal, because now it is impossible to say which database serves which purpose if you not have access to the k8s cluster.
example picture how it look today in Azure Portal if you provision some dbs with osba
(photomontage because I deployed only one DB on the testserver at the moment)
if you need to roll back a database from a service it is impossible to see which is the database for this service
It would be even better to be able to define a prefix for the random names but the tags would also help to keep track of purpose of these dbs.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
You support to set tags when provisioning a new "azure-sql-12-0" or "azure-sql-12-0-dbms" service, but it is not possible to set tags for a "azure-sql-12-0-database" service .
Since the name of the database cannot be determined, tags could help to identify the database in the azure portal and via CLI.
You already set a tag "heritage : open-service-broker-azure" on every new DB, so i hope the api exist to set tags for new DBs.
This would be very helpful to manage databases requested via osba in the azure portal, because now it is impossible to say which database serves which purpose if you not have access to the k8s cluster.
example picture how it look today in Azure Portal if you provision some dbs with osba
![image](https://user-images.githubusercontent.com/10489458/73288410-39c48a80-41fb-11ea-941f-3baaeb892c0a.png)
(photomontage because I deployed only one DB on the testserver at the moment)
if you need to roll back a database from a service it is impossible to see which is the database for this service
It would be even better to be able to define a prefix for the random names but the tags would also help to keep track of purpose of these dbs.
The text was updated successfully, but these errors were encountered: