az-hop/bicep
Xavier Pillons b7e1bd7d79
use MSI instead of SPN (#1907)
* az login with VM Identity

* remove containers

* update miniconda path

* update miniconda root install dir

* reuse container

* cleanup

* fix missing propertty due to latest bicep version

* use ACR token to authenticate

* add missing secrets

* add missing secrets

* add missing secrets

* remove SPN usage

* cleanup and API update
2024-05-13 17:25:47 +02:00
..
.yamllint
amlfs.bicep
anf.bicep use MSI instead of SPN (#1907) 2024-05-13 17:25:47 +02:00
azhop.bicep use MSI instead of SPN (#1907) 2024-05-13 17:25:47 +02:00
bastion.bicep
cleanup.sh
install.sh use newer api version (#1892) 2024-03-29 12:47:15 +01:00
jumpbox.yml
keyvault.bicep Enable PurgeProtection on KeyVault (#1893) 2024-03-29 14:45:48 +01:00
kv_access_policies.bicep
kv_secrets.bicep
mainTemplate.bicep Ubuntu 20.04 support (#1888) 2024-04-19 15:27:37 +02:00
mariadb.bicep
mysql.bicep fix api and empty property (#1870) 2024-03-05 11:02:46 +01:00
natgateway.bicep
network.bicep nsg and asg are contextuals to options (#1832) 2024-02-12 17:40:00 +01:00
nfsfiles.bicep
param.json
privatezone.bicep Support for multi-region queues (#1788) 2024-01-19 19:26:49 +01:00
privatezone_records.bicep
readme.md
roleAssignments.bicep
secrets.bicep
sig.bicep fix api and empty property (#1870) 2024-03-05 11:02:46 +01:00
storage.bicep
telemetry.bicep
vm.bicep don't create custom-data when empty (#1860) 2024-02-26 14:55:46 +01:00
vnetpeering.bicep
vpngateway.bicep

readme.md

Using bicep instead of Terraform

This is the scenario to provide compatibility with the existing mode of deploying using the local configuration file from either a local machine or an existing deployer VM.

  • from a local machine "az login" with your user name.
  • from a deployer VM "az login -i", the VM should have system assigned identity with the right roles as defined in the documentation.

From the root of the azhop directory run this

./build.sh -a <plan, apply> -l bicep