To connect a Looker project to GitHub by using HTTPS, use the developer settings in GitHub to create a personal access token. See GitHub's blog post for more information. GitHub does not accept account passwords for authenticating Git operations on.Note the following for GitHub HTTPS authentication: With HTTPS authentication, you can configure your LookML project to use a single Git account for the entire project, or you can configure the project to use your developers' individual Git accounts to perform their Git operations. Older Git versions will refuse to access repositories with this extension. The following options are available in either location: helper The name of an external credential helper, and any associated options. (which applies to all credentials), or credential.., where matches the context as described above.You can add or update configuration in this file with git config -worktree. CONFIGURATION OPTIONS Options for a credential context can be configured either in credential. Go to the Setting up HTTPS git connection with 2FA Enabled Community post to see instructions for creating personal access tokens for common Git providers. git config extensions.worktreeConfig true In this mode, specific configuration stays in the path pointed by git rev-parse -git-path config.worktree. If your Git account uses two-factor authentication, you can go to your Git provider and create access tokens to use instead of passwords. Looker uses a username and password (or access token) to log in to your Git provider and perform Git operations on behalf of your LookML developers. With SSH, Looker accesses your Git repository using a deploy key that you generate through your Git provider's website, as described in Connecting to Git Using SSH below.įor LookML projects configured with HTTPS authentication, Looker connects to your Git provider with one or more user accounts that you set up with your Git provider. With HTTPS, Looker accesses your Git repository with a username and password (or access token) that you provide, as described in Connecting to Git Using HTTPS below.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |