Open georgibakken opened 1 year ago
@georgibakken Hey Georg -- apologies for the delayed response; the above issue is an interesting one 🤔 Do you possibly have a past workflow where you ran docker build
against the Dockerfile in your repository that was successful? Maybe just a simple workflow that directly calls the command that's being executed within container-apps-deploy-action
:
docker build --tag KoermitApiRegistry.azurecr.io/github-action/container-app:3550347084.1 --file /home/runner/work/tina-labs-handbook/tina-labs-handbook/Dockerfile /home/runner/work/tina-labs-handbook/tina-labs-handbook
(you can tweak the tags and paths to get it to work)
I'm interested in comparing the logs that are produced from this successful run within a GitHub Actions workflow and the logs that you provided above that showed some of the steps being performed by container-apps-deploy-action
. As you mentioned, the environment variables set in your workflow specific to Tina.io are correctly propagated to the action, and you're using a Dockerfile and not our builder, so another container is not involved in this process (as far as I can tell), so some initial logs for comparison may help shed a little light if you're able to provide them whenever you have a chance to do so. Thanks!
Hi there,
I am trying to use the container-apps-adeploy-action for a nextjs application, specifically Tina.io.
Tina requires three env variables to be set when building, which I locally set in a .env with the variables
NEXT_PUBLIC_TINA_CLIENT_ID
,TINA_TOKEN
andNEXT_PUBLIC_TINA_BRANCH
. This work nicely locally when I build the docker image.In my GitHub action, I set them under
env
and read from GitHub secret. This is my workflow file:However I get an error from the action build job
Error: Client not configured properly. Missing branch, clientId, token. Please visit https://tina.io/docs/tina-cloud/connecting-site/ for more information
These values are set from the env variables
NEXT_PUBLIC_TINA_CLIENT_ID
,TINA_TOKEN
andNEXT_PUBLIC_TINA_BRANCH
.Another log from the action, is this:
Based on this, it looks as for me that the deploy action passes the correct env variables to docker, they are set and as far as I understand should be ready for
docker build
to read. Which is why I don't understand why the application throws the errors that the variables are not set/not configured.Any ideas on what is going wrong? Thank you!