No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

image.png

Hi all, I have small question, my provider v0.1.1 works fine, but I have one warning during execution, how to fix it or what is the cause?

Cause: It looks like the plugin your are developing with doesn’t serve the version correctly.
What framework are you using to serve the plugin?

this is my provider <https://github.com/wttech/pulumi-aem>, I've forked that from <https://github.com/pulumi/pulumi-provider-boilerplate>

`Version` is set in the <https://github.com/wttech/pulumi-aem/blob/7a2eb09720ab13cb6b715e2d26f527213b3171cf/Makefile#L11|Makefile> and then <https://github.com/wttech/pulumi-aem/blob/7a2eb09720ab13cb6b715e2d26f527213b3171cf/Makefile#L26-L27|embedded> into the <https://github.com/wttech/pulumi-aem/blob/7a2eb09720ab13cb6b715e2d26f527213b3171cf/provider/provider.go#L16|binary>. When I tried building your provider locally, the version I got was `"0.1.2-alpha.1716240557+7a2eb097.dirty"`. If you want to specify the version using the current Makefile, you need to build on a commit tagged at `v0.1.1`. You can check what version `pulumictl` will derive by running it directly:
```$ pulumictl get version```
If you want to hard-code that you are building version `v0.1.1` (instead of relying on git tags), you can run `VERSION=0.1.1 make provider`. That binary will report to have version v0.1.1.

Let me know if that helped.