This message was deleted.

So the chart creates CRDs for each of those things, and it’s up to you to call

apiextensions.CustomResource

with the right stuff in it?

well, based on what you are doing in your own libraries I did something like that :

export default class ClusterIssuer extends pulumi.CustomResource {
  readonly apiVersion: pulumi.Output<string>
  readonly kind: pulumi.Output<string>
  readonly metadata: pulumi.Output<any>
  private readonly __inputs

  /**
  * Create a certmanager.v1alpha1.ClusterIssuer resource with
  * the given unique name, arguments, and options.
  *
  * @param name The _unique_ name of the resource.
  * @param args The arguments to use to populate this resource's properties.
  * @param opts A bag of options that control this resource's behavior.
  */
  constructor (name, args, opts) {
    let inputs = {}
    inputs['apiVersion'] = '<http://certmanager.k8s.io/v1alpha1|certmanager.k8s.io/v1alpha1>'
    inputs['kind'] = 'ClusterIssuer'
    inputs['metadata'] = args && args.metadata || undefined
    // super(`kubernetes:${inputs.apiVersion}:${inputs.kind}`, name, inputs, opts)
    super('kubernetes:<http://certmanager.k8s.io/v1alpha1:ClusterIssuer|certmanager.k8s.io/v1alpha1:ClusterIssuer>', name, inputs, opts)
    this.__inputs = args
  }

  /**
   * Get the state of an existing `ClusterIssuer` resource,
   * as identified by `id`.
   * Typically this ID is of the form <namespace>/<name> ;
   * if <namespace> is omitted, then (per Kubernetes convention)
   * the ID becomes default/<name>.
   *
   * Pulumi will keep track of this resource using `name` as the Pulumi ID.
   *
   * @param name _Unique_ name used to register this resource with Pulumi.
   * @param id An ID for the Kubernetes resource to retrive. Takes the form
   *  <namespace>/<name> or <name>.
   */
  static get (name, id) {
    return new ClusterIssuer(name, undefined, { id })
  }

  getInputs () { return this.__inputs }
}

yeah, that sucks and I’m sorry to see it. All i can say is that we will mature with the ecosystem. 🙂

sure, but am I doing it right this way in the meantime ?

this looks like what you’d approximately want, yes.

haha, thanks. Any idea why if I change things in the spec (so the

args

parameter) a

pulumi up

don’t detect it and does not want to refresh the resource ?

uh

Sure no worries, have a good evening, thanks

@faint-motherboard-95438 thanks so much for your work! I’d love to turn your problems into canonical solutions. Was it just the CRD stuff

About the update detection ? Actually I’m not sure, but I was missing to initialize 2 values in

inputs

in the

constructor

:

inputs['spec'] = args && args.spec || undefined
    inputs['status'] = args && args.status || undefined

I think after that, it worked as expected.

ah

I could try to make a dedicated package for

cert-manager

in typescript if that makes sense to do it, or will it be quickly outdated if you are able to generate everything from any chart soon

I'm glad I saw this--I'm about to embark on fixing my k8s cluster at home to be Pulumi-based rather than just-a-bunch-of-YAML, and I'd definitely need cert-manager. 😄

@important-carpenter-15282 if you can give me a few days I’ll share a package with what I did, or if you are in a hurry I can send you a bunch of files dedicated to gcloud atm, I’d like to make it cloud agnostic.

I'm not in a hurry, no. Bare metal cluster for me, so cloud-specific stuff will not be super helpful. 😄

@important-carpenter-15282 I was planning to do something agnostic (well, as much as I can), I’ll share it with you and we’ll see how we can work this out 🙂

i've got a working cert-manager typescript using the helm chart and CRDs for issuer + certificate, happy to share.. i was going to make a package but didnt know how to do it properly

@better-rainbow-14549 would definitely be interested to see it 🙂