Yes, it does. Looks like we were running our code on creation, not on subsequent no-op reconciliations, and the way ApplyT works obscured an error that was happening as well. Looks like using stack exports and handling this outside of our Pulumi program is gonna be a bit nicer, in this case