-
Notifications
You must be signed in to change notification settings - Fork 7
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
Resource plugin version mismatch despite no conflicting binaries #477
Comments
@IaroslavTitov could this be a side-effect of the ci-mgmt change? |
Yes, I think you're right, likely version is not passed in someplace it needs to be.. I'll take a look |
### Summary - Fixes: #477 - Fixes the first bullet point of #465 - Fixing missed Version insertion using -ldflags - Moving location of Version to main.go to eliminate empty file - Moving serve.go logic to main.go to pull out serving logic out of provider package - Minor cleanup of Makefile - creating one BUILD_PATH variable to avoid repeating path blocks - Adding missed version specification for java sdk generation ### Summary - Tested build works locally and provider works as expected - Integ tests
Still seeing this on 0.27.4 |
@kdawgwilk The most likely reason for this is because we haven't published a new version of this provider. The fix should become available when a new version is released. |
This issue has been addressed in PR #486 and shipped in release v0.29.0. |
What happened?
When I run
p up
orp pre
and my Pulumi app uses the Pulumi Service provider, as of version 0.27.3, it returns the following warningNot affected:
0.27.1
Affected:
0.27.2
and0.27.3
While the warning is annoying this doesn't seem to affect the management of resources.
Example
Output of
pulumi about
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).
The text was updated successfully, but these errors were encountered: