Refactor exports to return Stack instead of Output[Exports] #340
Assignees
Labels
area/core
The SDK's core code
area/docs
The documentation and website
area/examples
Usage examples
impact/breaking
Fixing this issue will require a breaking change
impact/first-48
This bug is likely to be hit during a user's first 48 hours of product evaluation
Milestone
Comments
lbialy
added
area/core
|
yay, done! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Final value returned from a Besom program (Exports) is currently expected to arrive wrapped in Output. This was done to simplify final for-comp required for evaluation of all related resource constructors. This however messes up the dry run results when a dynamic Output is interwoven into the final for-comp because of the short-circuiting logic of dry run handling. To solve this a new case class called Stack has to be defined and the main function's signature has to be changed from
Context ?=> Output[Exports]toContext ?=> Stack.Stackwill have to contain two fields:exports(the old mechanism is to be used here) anddependsOnwhich could be a vararg to take all the resources that are to be created in this stack but aren't used for exports directly.The text was updated successfully, but these errors were encountered: