GitCredential
laktory.models.resources.databricks.GitCredential
ยค
Bases: GitCredentialBase
Databricks Git Credential
Examples:
import io
from laktory import models
credential_yaml = '''
git_provider: gitHub
git_username: my-user
personal_access_token: ${vars.git_pat}
'''
credential = models.resources.databricks.GitCredential.model_validate_yaml(
io.StringIO(credential_yaml)
)
References
| BASE | DESCRIPTION |
|---|---|
force
|
specify if settings need to be enforced (i.e., to overwrite previously set credential for service principals)
TYPE:
|
git_email
|
The email associated with your Git provider user account. Used for authentication with the remote repository and also sets the author & committer identity for commits
TYPE:
|
git_provider
|
case insensitive name of the Git provider. Following values are supported right now (could be a subject for a change, consult Git Credentials API documentation):
TYPE:
|
git_username
|
user name at Git provider. For most Git providers it is only used to set the Git committer & author names for commits, however it may be required for authentication depending on your Git provider / token requirements
TYPE:
|
is_default_for_provider
|
boolean flag specifying if the credential is the default for the given provider type
TYPE:
|
name
|
the name of the git credential, used for identification and ease of lookup
TYPE:
|
personal_access_token
|
The personal access token used to authenticate to the corresponding Git provider. If value is not provided, it's sourced from the first environment variable of
TYPE:
|
principal_id
|
The ID of the service principal whose credentials will be managed. Only service principal managers can use this field. When specified, the git credential is created or updated for the given service principal instead of the calling user
TYPE:
|