Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bad version declared #14 is still not fixed #16

Closed
JonAStorelv opened this issue Nov 23, 2022 · 1 comment
Closed

Bad version declared #14 is still not fixed #16

JonAStorelv opened this issue Nov 23, 2022 · 1 comment
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed

Comments

@JonAStorelv
Copy link

JonAStorelv commented Nov 23, 2022

What happened?

When trying to deploy cert manager, I get the same warning that should be fixed in issue#14
warning: resource plugin kubernetes-cert-manager is expected to have version >=0.0.3, but has 0.0.1; the wrong version may be on your path, or this may be a bug in the plugin

Steps to reproduce

put the example with my own "settings"

npm install @pulumi/kubernetes-cert-manager

run a pulumi up

Expected Behavior

The warning shouldn't appear

Actual Behavior

bad version reported

Output of pulumi about

CLI
Version      3.47.1
Go Version   go1.19.2
Go Compiler  gc

Plugins
NAME                     VERSION
azure-native             1.40.0
azuread                  5.6.0
kubernetes               3.8.2
kubernetes-cert-manager  0.0.3
nodejs                   unknown
random                   4.3.1

Host
OS       Microsoft Windows 11 Pro
Version  10.0.22000 Build 22000
Arch     x86_64

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@JonAStorelv JonAStorelv added the kind/bug Some behavior is incorrect or out of spec label Nov 23, 2022
@guineveresaenger guineveresaenger added the resolution/fixed This issue was fixed label Nov 24, 2022
@guineveresaenger
Copy link
Contributor

Hi @JonAStorelv - please try with v0.0.5 which should have successfully published a version. :)

Fixed in #17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Projects
None yet
Development

No branches or pull requests

2 participants