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
Hi All,
I am trying to use the azure approach but it seems that it is lacking some documentation; I was trying follow some examples but I get error as following:
echo "H4sIAAAAAAAA/0TOQUvEMBAF4Ht+xWPxHMSLmFtZBAUFEf9Atp20kXGmTJKq/fXSutDTDO/Bx3OPZmoB+8GlZR6yjOjeX3FWSXkMmJliIZCUZoRfbZjiQshSamSmAd26FeeXZyxkJavgzt/6+weoQeibzF/5OVrZ9M+iAqPSuCKZfqFOdCgBHJv0077jCOmH+oBTXE//f6vxwoSUmSBakbTJgCy4ees+nrxz7g8AAP//AQAA//8tKU8k3AAAAA==" | base64 -d | gunzip
Error: Error building ARM Config: please ensure you have installed Azure CLI version 2.0.79 or newer. Error parsing json result from the Azure CLI: launching Azure CLI: exec: "az": executable file not found in $PATH.
apiVersion: tf.upbound.io/v1beta1
kind: Workspace
metadata:
name: pipeline
spec:
providerConfigRef:
name: default
forProvider:
# Workspaces default to using a remote source - like workspace-remote.yaml.
# For simple cases you can use an inline source to specify the content of
# main.tf as opaque, inline HCL.
source: Inline
module: |
// Outputs are written to the connection secret.
resource "random_id" "example" {
byte_length = 4
}
@danielkimuipath The error message indicates that the provider is trying to use the Azure CLI which is not installed in the pod.
I don't know if anyone has tested the azurerm Terraform backend. If it requires the Azure CLI then it may not be supported. Can you try the same Workspace with backend kuberenetes and see if that works?
There is more info in #73 which seems to have worked.
What happened?
Hi All,
I am trying to use the azure approach but it seems that it is lacking some documentation; I was trying follow some examples but I get error as following:
How can we reproduce it?
ProviderConfig
Provider
Workspace
What environment did it happen in?
Crossplane version:
upbound/crossplane:v1.13.2-up.2
The text was updated successfully, but these errors were encountered: