little-soccer-569311/15/2022, 12:18 AM
little-cartoon-1056911/15/2022, 12:30 AM
bumpy-ice-2102411/15/2022, 12:49 AM
little-cartoon-1056911/15/2022, 12:56 AM
bumpy-grass-5450811/15/2022, 6:13 AM
not running the user program? if that changes in the future would it be mandatory? I am building some services that make heavy use of the Automation API and currently getting away with not passing any program to the workspace/stack when destroying.
little-cartoon-1056911/15/2022, 6:20 AM
echoing-dinner-1953111/15/2022, 9:22 AM
I can't see any advantage for Pulumi to run our code on destroy: everything it needs to destroy a stack is in state.That is true today, but there are some features people ask for (like delete hooks) which wouldn't be able to be stored fully in state and so we would have to run the program to get hold of them. It's likely that we would do a best effort to only run the program iff we saw the state had reference to new features that needed it, so if you weren't using those features you'd be able to continue running destroy without the program.
bumpy-grass-5450811/15/2022, 1:35 PM
little-soccer-569311/15/2022, 5:36 PM