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
{{ message }}
This repository has been archived by the owner on Oct 12, 2018. It is now read-only.
(jsone_template in this case is equivalent to a yaml parser, as there are no JSON-e operators or expressions in the input)
Terraform apply creates the resource correctly:
tf@eb5a5de314f4:/repo/tf$ kubectl get --ignore-not-found clusterissuer/letsencrypt-issuer
NAME AGE
letsencrypt-issuer 18m
and
tf@eb5a5de314f4:/repo/tf$ terraform state show module.taskcluster.k8s_manifest.certificate_clusterissuer
id = /apis/certmanager.k8s.io/v1alpha1/letsencrypt-issuer
content = {"apiVersion":"certmanager.k8s.io/v1alpha1","kind":"ClusterIssuer","metadata":{"name":"letsencrypt-issuer","namespace":"default"},"spec":{"acme":{"email":"[email protected]","http01":{},"privateKeySecretRef":{"name":"letsencrypt-staging"},"server":"https://acme-staging-v02.api.letsencrypt.org/directory"}}}
but the resulting 'id' seems to cause issues on subsequent terraform runs:
* module.taskcluster.k8s_manifest.certificate_clusterissuer: k8s_manifest.certificate_clusterissuer: /google-cloud-sdk/bin/kubectl kubectl get --ignore-not-found v1alpha1/letsencrypt-issuer exit status 1: the server doesn't have a resource type "v1alpha1"
The selfLink for the resource is /apis/certmanager.k8s.io/v1alpha1/letsencrypt-issuer, so
naturally produces that k8s resource name. I'm not sure where the bug is, here -- is there a spec for the format of the selfLink that is being violated here?
I have a CRD:
and I'm trying to create an object of its type:
with
(jsone_template in this case is equivalent to a yaml parser, as there are no JSON-e operators or expressions in the input)
Terraform apply creates the resource correctly:
and
but the resulting 'id' seems to cause issues on subsequent terraform runs:
The selfLink for the resource is
/apis/certmanager.k8s.io/v1alpha1/letsencrypt-issuer
, soterraform-provider-k8s/main.go
Lines 190 to 195 in 6a55723
naturally produces that k8s resource name. I'm not sure where the bug is, here -- is there a spec for the format of the selfLink that is being violated here?
/cc @imbstack
The text was updated successfully, but these errors were encountered: