How do you provide the filepath to the metadata

[codeBehindMe]

Question

So I'm not sure what i'm doing wrong here. But I keep a running: gcloud beta run services replace service.yaml --platform managed --region australia-southeast1 Error: ERROR: (gcloud.beta.run.services.replace) argument FILE: Failed to load YAML from [service.yaml]: Unable to read file [service.yaml]: [Errno 2] No such file or directory: 'service.yaml' error.

I have copied the service.yaml file to every single possible location. relative to the directory path. i.e.
it is now at root of the repo; it is also at the .github folder. it's also at the .github/workflows folder. It is also at the repo_root/infrac/service.yaml location.

[sethvargo]

The GITHUB_WORKSPACE environment variable will point to the workspace directory path. Initially this is empty, until you run actions/checkout. Depending on your setup, this could be a different directory than the current working directory. So if the service.yaml is in your repo, you could specify the absolute path to avoid needing to find the relative location:

gcloud beta run services replace $GITHUB_WORKSPACE/service.yaml ...

[erikw]

@codeBehindMe I came here as I had the same issue. For me I turned out that debugging that I had disabled the actions/checkout step, thus the repo and the service.yaml was not available. This could maybe be the case for you as well?

[averikitsch]

use the metadata input with the relative path to the file, ex:

deploy-cloudrun/.github/workflows/deploy-cloudrun-it.yml

Line 183 in 07a7b6c

metadata: ./tests/unit/service.full.yaml