Describes an existing Snowflake Git repository clone.
ALTER GIT REPOSITORY, CREATE GIT REPOSITORY, DROP GIT REPOSITORY, SHOW GIT BRANCHES, SHOW GIT REPOSITORIES, SHOW GIT TAGS
{ DESC | DESCRIBE } GIT REPOSITORY <name>
Copy
Parameters¶name
Specifies the identifier for the Git repository clone to describe.
If the identifier contains spaces or special characters, the entire string must be enclosed in double quotes. Identifiers enclosed in double quotes are also case-sensitive.
For more information, see Identifier requirements.
The command output includes properties in the following columns:
Column
Description
created_on
Date the Git repository clone was created.
name
Name of the Git repository clone.
database_name
Name of the database containing this Git repository clone.
schema_name
Name of the schema containing this Git repository clone.
origin
URL of the remote Git repository’s origin.
api_integration
Name of the API integration included in this Git repository clone.
git_credentials
Name of the secret object in this Git repository clone.
owner
Role used when this Git repository clone was created.
owner_role_type
Type of role that owns the object, either ROLE or DATABASE_ROLE.
comment
Comment specified when this Git repository clone was created.
Access control requirements¶A role used to execute this operation must have the following privileges at a minimum:
Privilege
Object
Notes
OWNERSHIP
Git repository
OWNERSHIP is a special privilege on an object that is automatically granted to the role that created the object, but can also be transferred using the GRANT OWNERSHIP command to a different role by the owning role (or any role with the MANAGE GRANTS privilege).
For instructions on creating a custom role with a specified set of privileges, see Creating custom roles.
For general information about roles and privilege grants for performing SQL actions on securable objects, see Overview of Access Control.
Usage notes¶To post-process the output of this command, you can use the pipe operator (->>) or the RESULT_SCAN function. Both constructs treat the output as a result set that you can query.
The output column names for this command are generated in lowercase. If you consume a result set from this command with the pipe operator or the RESULT_SCAN function, use double-quoted identifiers for the column names in the query to ensure that they match the column names in the output that was scanned. For example, if the name of an output column is type, then specify "type" for the identifier.
The following example generates a description of the snowflake_extensions Git repository clone:
DESCRIBE GIT REPOSITORY snowflake_extensions;
Copy
The preceding command generates output such as the following:
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | CREATED_ON | NAME | DATABASE_NAME | SCHEMA_NAME | ORIGIN | API_INTEGRATION | GIT_CREDENTIALS | OWNER | OWNER_ROLE_TYPE | COMMENT | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | 2023-06-28 08:46:10.886 -0700 | SNOWFLAKE_EXTENSIONS | MY_DB | MAIN | https://github.com/my-account/snowflake-extensions.git | GIT_API_INTEGRATION | MY_DB.MAIN.GIT_SECRET | ACCOUNTADMIN | ROLE | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4