prehistoric-account-60014
04/09/2020, 11:05 PMgs://
URLs when using RemoteAsset
or RemoteArchive
for the BucketObject
source
?white-balloon-205
RemoteAsset
- so great to hear you are interested in using it - would love to hear more about the use case.
Definitely feel free to open an issue to support it. One slight challenge will be credentials - it isn’t immediately clear which credentials this should use.prehistoric-account-60014
04/10/2020, 12:39 AMdocker.Image
and FileArchive
for gcp.cloudfunctions.Function
. The reason being that these artifacts shouldn’t be deleted when re-running pulumi up
. They’re not “persistent infrastructure” but more of a side-effect of a build and Pulumi should probably only be used for “persistent infrastructure”…faint-table-42725
04/10/2020, 2:04 AMprehistoric-account-60014
04/10/2020, 2:37 AMpulumi up
and deploy any existing artifact to roll back, for example.faint-table-42725
04/10/2020, 2:41 AMprehistoric-account-60014
04/10/2020, 6:37 PMdocker.Image
a lot in the documentation so it would seem that it’s recommended, but it stays pretty high level and never goes into how one would manage multiple versions of these images. Just interpolating the version wouldn’t work since Pulumi would delete the older version when running pulumi up
, no?curved-ghost-20494
06/10/2020, 1:19 PMprehistoric-account-60014
06/10/2020, 1:34 PMpulumi up
with a different version would destroy the artifact. So our decision was to avoid using Pulumi for artifacts and instead only use it for deployments (i.e., something that should change when you run pulumi up
, a declarative representation of some state the infrastructure should be in).white-balloon-205
Just interpolating the version wouldn’t work since Pulumi would delete the older version when runningNo - this shouldn't be true - though maybe I don't understand exactly the scenario you have in mind?, no?pulumi up
docker.Image
doesn't delete images currently, it only ever creates them.
With artifacts you really want to just upload them and then never touch them, they’re supposed to be immutable.It is definitely valid to want to separate the process of producing artifacts from the
pulumi
deployment itself. You can then couple then use deltas to the Pulumi deployment to mark the deployment of a specific artifact, but version the artifacts out of band. That said, for docker Images in particular, it should be possible to push these without losing immutable artifact deployments.curved-ghost-20494
06/10/2020, 10:39 PMprehistoric-account-60014
06/10/2020, 10:41 PMdocker.Image
doesn’t delete the image. In our case we were also using GCS for artifacts and gcp.storage.BucketObject
does get deleted on pulumi up
. In this case the artifacts were GCP cloud function source zip archives