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
This commit was created on GitHub.com and signed with GitHub’s verified signature.
The key has expired.
NEW: You can now use Kubernetes as a compute platform for leveraging database builds with the new sbm k8s commands. See the Kubernetes documentation for background, information and how-to examples
NEW: You can now use Azure Container Instance as a compute platform for leveraging database builds with the new sbm aci commands. See the ACI documentation for background, information and how-to examples
ADDED: New Azure Key Vault integration -- secrets can now be stored in Key Vault and no longer need to be stored in the settings file or passed via command line. See the documentation here
IMPORTANT: Batch node pools are now created with assigned Managed Identities. Because of this, the workstation running sbm needs to have a valid Azure authentication token. This can be done via Azure CLI az login, Azure PowerShell Connect-AzAccount, or if running from an automation box, ensure that the machine itself has a Managed Identity that has permissions to create Azure Batch resources.
UPDATED: Automation scripts /scripts/templates have been updated to simplify the creation of Azure resources, runtime, secrets file and pushing secrets to Key Vault. See info here
UPDATED: Batch and Kubernetes now have Managed Identity assigned to allow seamless access to Key Vault