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
Imagine a sample that tries to setup a developer’s environment with one, two, or three different containers – only one is SQL. Docker commands are enough, but sqlcmd is easier – or at least could be. To do this, the password to access SQL will be key.
The requirement would simple be:
Allow a known password to be passed in.
Allow a generated password to be extracted. (not in an interactive way, but a programmatic way)
The text was updated successfully, but these errors were encountered:
We are looking at solving this with add-ons (in the same way Azure Container Apps does), so secret management is completely abstracted away from the user. There is a rough POC of this in #319 that can be used for demo purposes:
Sets up an environment (a sqlconfig context) with two containers, one SQL Server container, and one Azure Data Builder container. The password management is done for you by sqlcmd. This command line goes onto clone the sample repo, and loads VS Code, all the user has to do to launch the application is press F5 in VS Code.
To clean up all the containers, the use just does "sqlcmd delete"
Sets up an environment (a sqlconfig context) for a multi-tenant application, using three containers, one SQL Server container, one Azure Data Builder container and one Azure Database Fleet Manager container. The password management is done for you by sqlcmd.
Imagine a sample that tries to setup a developer’s environment with one, two, or three different containers – only one is SQL. Docker commands are enough, but sqlcmd is easier – or at least could be. To do this, the password to access SQL will be key.
The requirement would simple be:
The text was updated successfully, but these errors were encountered: