This message was deleted.
# generals
sparse-intern-71089
11/11/2021, 2:07 PMThis message was deleted.
✅ 1
s
sparse-spring-91820
11/11/2021, 2:08 PMThis is a screenshot of the error
l
little-cartoon-10569
11/11/2021, 7:39 PMGenerally this happens when a stack is deployed with one version of the plugin from one machine, and different version is installed on another machine. Usually (for me) the "error" machine only has the new version, but the most recent deployment happened from another machine with an older version of the plugin.
little-cartoon-10569
11/11/2021, 7:40 PMYour options are
1) to install the old plugin and deploy from this machine; the old version of the plugin is needed to read, but the new version will be used when writing, and then everything is good (you can remove the old version of the plugin).
little-cartoon-10569
11/11/2021, 7:41 PMor
2) to install the latest version on some other (dev) machine, manually deploy (upgrading the plugin associated with the resources), and then run the CircleCI pipeline.
little-cartoon-10569
11/11/2021, 7:42 PMThe most robust solution for a pipeline is to detect these errors and resolve them in the pipeline, since they do happen every few weeks in my experience.
little-cartoon-10569
11/11/2021, 7:42 PMFortunately the error message includes the command that resolves it.
s
sparse-spring-91820
11/11/2021, 9:05 PMThank you for your answer!
I only deployed from one machine which is circleci executor and don't understand how that caused error you described 🤔
Can pulumi somehow address this problem by maybe looking at package.json package versions and automatically install proper plugin so that they are all same on every machine?
l
little-cartoon-10569
11/11/2021, 9:19 PMYes in general it does that, but occasionally the version in the state is different to the version available to Pulumi. When you're caching / retaining your plugins, then both versions are available and you don't see this problem; if the old versions are gone (maybe you're creating a new ~/.pulumi each time you build) then you have only the newest plugin available, and the older one is still being referenced in the state.
little-cartoon-10569
11/11/2021, 9:20 PMThe best thing to do is to add ~/.pulumi to whatever caching CircleCI offers, so you always keep all versions of the plugins. If you can't do that, then you need to be able to install both the newest and currently in-use versions of each plugin for each deployment.
s
sparse-spring-91820
11/11/2021, 10:03 PMThanks @little-cartoon-10569 a lot! 🙌
👍 1
3 Views