Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

Cannot create container registry #199

Open
davemaul opened this issue Aug 9, 2022 · 0 comments
Open

Cannot create container registry #199

davemaul opened this issue Aug 9, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@davemaul
Copy link

davemaul commented Aug 9, 2022

What happened?

I tried to create a container registry with this provider. The process failed with the following error message:

observe failed: cannot run refresh: refresh failed: Missing required
argument: The argument "encryption.0.identity_client_id" is required,
but no definition was found.: File name: main.tf.json

Missing required argument: The argument "encryption.0.key_vault_key_id"
is required, but no definition was found.: File name: main.tf.json

This is weird because I don't want to use encryption at all. The field is optional as documented here. I tried to fix it by setting encryption.enabled: false but this didn't work out either.

How can we reproduce it?

apiVersion: containerregistry.azure.jet.crossplane.io/v1alpha1
kind: Registry
metadata:
  name: registry
  namespace: {{ .Release.Namespace }}
spec:
  forProvider:
    name: {{ .Values.registryName }}
    resourceGroupName: {{ .Values.rg }}
    location: {{ .Values.location }}
    adminEnabled: true
    sku: Basic
  providerConfigRef:
    name: provider-jet-azure

This is a fairly simple setup.

What environment did it happen in?

Crossplane version: v1.9.0
Provider Version: v0.12.0-preview
Kubernetes: AKS 1.23.8

Thanks in advance!

@davemaul davemaul added the bug Something isn't working label Aug 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant