This message was deleted.

Yeah - the simplest thing which is fairly common is just to shell out to some build task inside an apply. That apply can depend on outputs of some resources, and then the output of the apply can be an input to other resource(s) so that the build task becomes part of the normal dependency graph. The only downside of this is that the build task will run on every update - even if “nothing has changed”. If that is not acceptable for a use case, dynamic providers can be used to customize the “diff” and “update” logic to be smarter about what work to do when there are (or are not) changes to inputs. The Docker build package does the simple thing above today fwiw.

Thanks for this, dug into the docker code and found that. Didn't realise that Outputs can wrap promises then it will get resolved nicely.