gorgeous-alarm-2929511/23/2023, 4:23 AM
and then various stacks such as
can be used to provide overrides.
Is it possible to have resources in different files such as a
for VPC and Networking etc and then another one for Storage and so on ?
I would also like to understand if it is possible to share output among these files?
gifted-gigabyte-5385911/23/2023, 9:15 AM
quick-machine-3031911/23/2023, 11:43 AM
gorgeous-alarm-2929511/23/2023, 5:00 PM
Are you looking to have multiple stacks for those different things you mention, and then integrate them (e.g. use the subnets created in the networking stack as an input to the storage stack)?Correct. that is what I am looking. Thanks for linking the issue @gifted-gigabyte-53859 It is exactly what I looking for. 🙂
little-cartoon-1056911/23/2023, 8:30 PM
Is it possible to have resources in different files such as a Pulumi.yaml for VPC and Networking etc and then another one for Storage and so on ?This is what projects are for. You can have a networking project (with stacks), a storage project (with stacks), etc. In general, different stacks from a single project shouldn't refer to each other. It becomes too hard to manage deployment order and dependencies. When projects are used for this purpose, there's generally no problem defining deployment order: networking must be deployed before storage. But stacks contain different copies of the same resources, so why would stackX have to be deployed before (or after) stackY? They're non-overlapping copies of the same resources, so they're independent by definition.
gorgeous-alarm-2929511/23/2023, 9:19 PM
2. The project then has stacks corresponding to env like gcp-dev, gcp-staging, and gcp-prod
3. The project also has various resources (in different yaml files) such as VPCs, GKE cluster, buckets etc
4. These config for resources can be managed under the stack, such a gcp-dev specifies the regions and project for all resources
little-cartoon-1056911/23/2023, 11:41 PM
option described here: https://www.pulumi.com/docs/languages-sdks/yaml/#compiler-support