Idempotent deployment on each google cloud build: is it a bad idea?

[Edmondo Porcu]

Hello Googlers,

I have a number of services which I would like to deploy, and each of them deploys a number of resources: some of them are common such as an object storage bucket or a pub/sub topic used to communicate among them and therefore the first one that runs should create them.

Although a create or update behaviour can be easily achieved with scripts, I would have expected a create-or-update mode to be available in the sdk. Is there a particular reason why it is not supported, such as "you are doing a bad thing and you are not realizing it?"

Thanks

Ed

[David (Google Cloud Support)]

As mentioned by documentation, Cloud Build is a service made to execute builds on GCP infrastructure, all depending on your specification. These builds use source codes from various repository services like Cloud Storage, Cloud Source Repositories, Github, etc, which is where you would be creating and updating your applications and services to your liking.

If you would like to specify different build specification, the point is that you can deploy a new Cloud Build for it, which would act as updating it. If I misunderstood what you meant and believe that the updating feature is indeed missing from Cloud Build, you can always submit a Feature Request and it will perhaps be added in the future, with no ETA nor any guarantee on its fulfilment however. Providing details and the expectations of what your desired feature would accomplish is always greatly useful for understanding what should be added.