I assume you are working off

pulumi-master

of your fork?

Yep.

OK, I’ll PR to that fork. I have commit access to upstream to the official provider also

We’ve in general tried to stick to the latest release from upstream. If there’s really critical fixes or new features though - we can consider pulling in something newer.

Hah, ignore that. There is a newer release than what I had, which is the current tip of master.

FWIW - I pulled current status this morning:

Provider | Our Version | Our Version Date | Current Version | Current Version Date | Next Version | Age
-- | -- | -- | -- | -- | -- | --
Azure | 1.6.0 | 5/24/18 | 1.12.0 | 8/3/18 | 1.13.0 | 71
OpenStack | 1.6.0 | 6/20/18 | 1.7.0 | 8/1/18 | 1.8.0 | 42
AWS | 1.26.0 | 7/4/18 | 1.30.0 | 8/2/18 | 1.31.1 | 29
GCP | 1.16.2 | 7/18/18 | 1.16.2 | 7/18/18 | 1.17.0 | 0

Yup. Have you been merging rather than rebasing?

Yes - we’ve been merging. We also have a tool we use to update

Gopkg.lock

based on upstream deps to make sure we are picking up the same dependencies in final build.

Ah ok, I might leave updating that to you then :-)