This message was deleted.

fwiw this is what I though

this.RegisterOutputs()

was doing under the hood, but that doesn't appear to be the case

You can expose an output that uses All and Apply to wait on multiple inputs, but resolve to the value of just one. This can give you back a single output that waits for everything you want to make sure is created before using it. RegisterOutputs does work for dependsOn, as a way to indicate what other resourcss must be transitively depended on, but individual outputs you store on the component don’t by default know they should be coupled to the component itself. I do think we may want to add a helper which lets you mix the component (and its inferred transitive dependencies) into an output as part of assigning it to an output on the component.

You can expose an output that uses All and Apply to wait on multiple inputs, but resolve to the value of just one. This can give you back a single output that waits for everything you want to make sure is created before using it.

Yeah that's what I did, which isn't too counter intuitive but the semantics are definitely suboptimal. I was looking through the source a bit and it seemed like it might be possible to gate the completion sources somehow