Environment
Device and OS:
App version:
Kubernetes distro being used:
Other:
Steps to reproduce
- Make an Internal repo in GitLab with a task file in it.
- Make another repo in GitLab that has a tasks.yaml file that
includes: the internal repo's task file
- In the latter repo try to run a maru task in
.gitlab-ci.yml after setting the MARU_AUTH env var to
variables:
MARU_AUTH: '{"gitlab.example.com": "$CI_JOB_TOKEN"}'
$CI_JOB_TOKEN is a GitLab Built-In variable. Read more about it here.
Expected result
It works
Actual Result
It doesn't work, because Maru uses the GitLab Files API, which $CI_JOB_TOKEN isn't allowed to use
Visual Proof (screenshots, videos, text, etc)
Severity/Priority
Medium I'd say? We're having to do some suuuuuper gross things with Group Tokens to get around this major limitation, but it isn't an immediate show-stopper.
Additional Context
This doesn't work only because $CI_JOB_TOKEN isn't allowed to use the Files API. It IS allowed to git clone. So, the likely route forward is changing Maru's includes: logic so that it does a git clone rather than using an API.
Environment
Device and OS:
App version:
Kubernetes distro being used:
Other:
Steps to reproduce
includes:the internal repo's task file.gitlab-ci.ymlafter setting theMARU_AUTHenv var toExpected result
It works
Actual Result
It doesn't work, because Maru uses the GitLab Files API, which $CI_JOB_TOKEN isn't allowed to use
Visual Proof (screenshots, videos, text, etc)
Severity/Priority
Medium I'd say? We're having to do some suuuuuper gross things with Group Tokens to get around this major limitation, but it isn't an immediate show-stopper.
Additional Context
This doesn't work only because $CI_JOB_TOKEN isn't allowed to use the Files API. It IS allowed to
git clone. So, the likely route forward is changing Maru'sincludes:logic so that it does agit clonerather than using an API.