Skill · artefacts · Run an artefact repository
Grant targeted access to an artefact repository and prove it opens one door only
Create a service account and grant it a targeted role on a single repository, then prove both halves of the contract, what the account can do and what it must not be able to do. Tell API control apart from download control, governed by two different mechanisms, and know that a fresh account is already read-only.
Start lesson 1The artefacts domain
- 1 lesson
- ~55 min of reading
- 1 quiz
- 1 proof lab
The path
Where it comes from, where it leads
What you need to know first, where you stand on this skill, and what it opens next. Your status is computed in your browser, from what you have read and passed.
Before · 1 prerequisite
This skill, for you
Grant targeted access to an artefact repository and prove it opens one door only
Computing
It unlocks · nothing yet
No other skill requires it: it is an end-of-path skill.
The path through the foundations From the most upstream foundation to this skill: what is in place, what remains to read.
Lessons
How to learn it
1 lesson, about ~55 min, in program order. Each lesson ends with its quiz.
The program
1 lesson · ~55 min
Beyond the lessons
Assess, practise, pass the proof
Reading a lesson confirms nothing. A skill is confirmed by a passed quiz, practised in a guided lab, and put to the test by a challenge or a mission; an imported lab result is not verified by the site.
Assess yourself
1 quiz
At the end of the lessons: passed at 70%, it confirms the skill.
Practice
No guided lab
No guided lab practices it yet.
Proof
1 practical proof
A practical proof is a challenge, a capstone or a declared lab.
Used by the mission “Run a trusted artefact repository”, which has its proof.
Placement test
Preparing the questions…
Your answers in detail
For each question asked: your answer, the correct answer, its explanation and the page to reread.
Around it
Who requires it, who teaches it
Required by
Taught by
Same block · Run an artefact repository
- Put an artefact repository into service and prove it answers, from the containerised instance to the CLI that drives it
- Proxy a public index and prove the cache still serves when the upstream becomes unreachable
- Host your own packages in an internal repository and have them installed from another machine
- Serve container images from your own repository, including a cache of a public registry
- Sign a repository's artefacts and make verification fail on an unsigned one
- Serve an artefact repository with no Internet access and bring content in by export and import
- Back up an artefact repository and prove the restore serves a client