After `crd2pulumi`'ing cert-manager crds, I'm tryi...
# typescript
s
After `crd2pulumi`'ing cert-manager crds, I'm trying to use the generated code, but can't figure out where this dependency comes from on
pulumi up
.
Copy code
Diagnostics:
  pulumi:providers:kubernetes (default_0_0_1):
    error: no resource plugin 'kubernetes-v0.0.1' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource kubernetes v0.0.1`
package.json
of my local autogenerated package:
Copy code
{
  "name": "@pulumi/depo-cert-manager",
  "version": "0.0.1",
  "scripts": {
    "build": "tsc"
  },
  "peerDependencies": {
    "@pulumi/pulumi": "^2.22.0"
  },
  "pulumi": {
    "resource": true
  },
  "devDependencies": {
    "typescript": "^4.2.3"
  }
}
loading that package in the main pulumi program
package.json
with:
Copy code
"dependencies": {
    "@pulumi/depo-cert-manager": "file:cert-manager-types",
What's causing pulumi to think of this package as a plugin? I changed to
"version": "0.0.2"
, and I get the following on `pulumi up`:
Copy code
Diagnostics:
  pulumi:providers:kubernetes (default_0_0_2):
    error: no resource plugin 'kubernetes-v0.0.2' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource kubernetes v0.0.2`
as one would predict, running that recommended fix results in:
Copy code
$ pulumi plugin install resource kubernetes v0.0.2

[resource plugin kubernetes-0.0.2] installing
error: [resource plugin kubernetes-0.0.2] downloading from : 403 HTTP error fetching plugin from <https://get.pulumi.com/releases/plugins/pulumi-resource-kubernetes-v0.0.2-linux-amd64.tar.gz>
Strange workaround, updating the npm package version to match the installed kubernetes plugin version bypasses that error
Copy code
"version": "2.8.2",
Copy code
$ pulumi up
[...]
     Type                                                              Name                                       Plan       Info
     pulumi:pulumi:Stack                                               haze-omega
 +   ├─ kubernetes:<http://cert-manager.io/v1:ClusterIssuer|cert-manager.io/v1:ClusterIssuer>                    letsencrypt-staging                        create
[...]