https://pulumi.com logo
#general
Title
# general
i

icy-controller-6092

01/07/2024, 12:34 AM
The pulumi docs really should not be recommending microstacks at this stage. There is just too much functionality missing to make microstacks a pleasant experience
d

dry-keyboard-94795

01/07/2024, 1:24 AM
What functionality would you like to see?
i

icy-controller-6092

01/07/2024, 2:07 AM
better config handling, previously you would have a project monostack and 1 yaml file per env-based stack now you have a matrix of yaml files, which is 1 for every microstack + env combination there's currently no way to share config, you have to repeat provider configs for every combination
2) be able to configure default providers using a StackReference
3) slice up the matrix dynamic, e.g sometimes you want to view all environments for a service microstack, other times you want to see all services for an environment. the current project > stack UI forces you to pick one of those
4) auto-stack creation on
pulumi up
5) make it MUCH easier to move resources between stacks. the only effective method right now is stack import/export with some painful JSON editing in between
d

dry-keyboard-94795

01/07/2024, 11:28 AM
On sharing configs and configuring default providers, this is something Pulumi ESC can solve, though you need to use Pulumi Cloud for it https://www.pulumi.com/product/esc/
i

icy-controller-6092

01/07/2024, 11:51 AM
ESC won’t work because sometimes for local developer deploys a local file state backend is used. Same program, just doesn’t need to use pulumi cloud for a developer deploy to a local machine