Thanks for the reply. I did see that point in the documentation however I didn’t think it applied here. I’m simply implementing the example on the Execution Modes page (Pipeline execution mode) and the details in the ‘Add inputs and outputs’ section, specifically how a bearer token is dynamically injected upon startup, works in a similar way to how the Source credentials are injected.
Today I took a slightly different approach and I tried this tutorial. It has the same basic output structure, is quite detailed and doesn’t mention additional steps to access the output resource. Again, I got the same DNS error upon attempting to write to the declared output stream.