I have a Hugo site and Hugo has a characteristic where it needs to know the base url at build time to generate absolute links properly.
The problem is that it creates a egg and chicken problem where I need the base url to build the site but I need the artifact to know for sure what could be the base url.
Right now I am not doing preview deployments so it's not a huge deal as I can just hardcode the hostname, but it will if someone wants to do preview deploys.
Basically what I suggest is that the workflow creates the slot at first, gives the base URL and confirms the deploy as a finish step, like those cleanup tasks some workflows have.
I have a Hugo site and Hugo has a characteristic where it needs to know the base url at build time to generate absolute links properly.
The problem is that it creates a egg and chicken problem where I need the base url to build the site but I need the artifact to know for sure what could be the base url.
Right now I am not doing preview deployments so it's not a huge deal as I can just hardcode the hostname, but it will if someone wants to do preview deploys.
Basically what I suggest is that the workflow creates the slot at first, gives the base URL and confirms the deploy as a finish step, like those cleanup tasks some workflows have.