This message was deleted.

It sounds like you want to use the resource outputs of an object that doesn't exist yet, to create that object. Which is obviously not going to work. Based on https://next-auth.js.org/getting-started/example,

NEXTAUTH_URL

looks intended to be a "friendly" name for a user to interact with. My guess is you need to pick a friendly name

<http://blah.mydomain.com|blah.mydomain.com>

and then create a the dns entry by hand or based on the output of

app.statuses[0].url.get()

.

Yeah it looks like best approach is to include a

DomainMapping

and then this way I can categorically know what my domain will be e.g.

<http://staging.domain.com|staging.domain.com>

and not use the dynamic url's that are output, this way it is safe. I think that this has to be set for production deploys rather than for users (AFAIK) - bit of a funny req