sparse-intern-71089
05/04/2023, 6:04 PMmillions-furniture-75402
05/04/2023, 6:36 PMIt’d be interesting if you could have multiple stacks that shared some state - ie. a project that was for a single microservice instance and a monolithic project that was for an entire environment that included the microservice. Obviously there’d be a challenge in reading multiple pieces of state across multiple storage areas (eg.GCS buckets) and co-ordination/locking.The popular method for achieving this is with a "shared-" or "base-" project that has the resources which other stacks share. The "child" stacks get the values of the Outputs via StackReferences, and use the resource getters to get a copy of the resource in the current scope. https://www.pulumi.com/blog/iac-recommended-practices-using-stack-references/
millions-furniture-75402
05/04/2023, 6:36 PMlemon-monkey-228
05/04/2023, 6:36 PMmillions-furniture-75402
05/04/2023, 6:37 PMlemon-monkey-228
05/04/2023, 6:37 PMmillions-furniture-75402
05/04/2023, 6:38 PMlemon-monkey-228
05/04/2023, 6:38 PMlemon-monkey-228
05/04/2023, 6:38 PMmillions-furniture-75402
05/04/2023, 6:38 PMlemon-monkey-228
05/04/2023, 6:38 PMmillions-furniture-75402
05/04/2023, 6:38 PMmillions-furniture-75402
05/04/2023, 6:40 PMshared-infrastructure
for your account-wide resources
2. shared-project-name
for resources shared across other stacks in a project (e.g. you have a 3 tier web application, and they all have to share some S3 bucket)
3. pulumi-components
for our "level 2" abstractions of our resources (e.g. custom resource) distributed as a library for Stacks to use to simplify resource declarationslemon-monkey-228
05/04/2023, 6:41 PMmillions-furniture-75402
05/04/2023, 6:41 PMmillions-furniture-75402
05/04/2023, 6:41 PMmillions-furniture-75402
05/04/2023, 6:42 PMmy-org/my-project/my-stack
.millions-furniture-75402
05/04/2023, 6:43 PMmy-org.my-project.my-stack
great-sunset-355
05/05/2023, 9:40 AMget_<resource>
functions.