Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix the internal document link typo in docs/auth.md #3567

Merged
merged 1 commit into from
Nov 30, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/auth.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,10 +33,10 @@ refers to `TaskRuns` and `PipelineRuns` as `Runs` for the sake of brevity.
- [A Workspace or Volume is also Mounted for the same credentials](#a-workspace-or-volume-is-also-mounted-for-the-same-credentials)
- [A Task employes a read-only-Workspace or Volume for `$HOME`](#a-task-employs-a-read-only-workspace-or-volume-for-home)
- [The Step is named `image-digest-exporter`](#the-step-is-named-image-digest-exporter)
- [Disabling Tekton's Built-In Auth](#disabling-tektons-build-in-auth)
- [Disabling Tekton's Built-In Auth](#disabling-tektons-built-in-auth)
- [Why would an organization want to do this?](#why-would-an-organization-want-to-do-this)
- [What are the effects of making this change?](#what-are-the-effects-of-making-this-change)
- [How to disable the built-in auth](#how-to-disable-the-build-in-auth)
- [How to disable the built-in auth](#how-to-disable-the-built-in-auth)

## Overview

Expand Down Expand Up @@ -599,7 +599,7 @@ TaskRun's `Pod template` field](./taskruns.md#specifying-a-pod-template).
If you require Steps to run with different UIDs then you should disable
Tekton's built-in credential initialization and use Workspaces to mount
credentials from Secrets instead. See [the section on disabling Tekton's
credential initialization](#disabling-tektons-build-in-auth).
credential initialization](#disabling-tektons-built-in-auth).

#### A Workspace or Volume is also Mounted for the same credentials

Expand All @@ -609,7 +609,7 @@ try to initialize.

The simplest solution to this problem is to not mix credentials mounted via
Workspace with those initialized using the process described in this document.
See [the section on disabling Tekton's credential initialization](#disabling-tektons-build-in-auth).
See [the section on disabling Tekton's credential initialization](#disabling-tektons-built-in-auth).

#### A Task employs a read-only Workspace or Volume for `$HOME`

Expand All @@ -619,7 +619,7 @@ credentials that Tekton will try to initialize.

The simplest solution to this problem is to not mix credentials mounted via
Workspace with those initialized using the process described in this document.
See [the section on disabling Tekton's credential initialization](#disabling-tektons-build-in-auth).
See [the section on disabling Tekton's credential initialization](#disabling-tektons-built-in-auth).

#### The contents of `$HOME` are `chown`ed to a different user

Expand Down