Lists the Git repository clones that you have privileges to access.
The SHOW STAGES command also lists Snowflake Git repositories. In the SHOW STAGES output, a Snowflake Git repository has the value GIT REPOSITORY in its type column.
ALTER GIT REPOSITORY, CREATE GIT REPOSITORY, DESCRIBE GIT REPOSITORY, DROP GIT REPOSITORY, SHOW GIT BRANCHES, SHOW GIT TAGS
SHOW GIT REPOSITORIES [ LIKE '<pattern>' ]
[ IN
{
ACCOUNT |
DATABASE |
DATABASE <database_name> |
SCHEMA |
SCHEMA <schema_name> |
<schema_name>
}
]
[ LIMIT <rows> [ FROM '<name_string>' ] ]
Copy
Parameters¶LIKE 'pattern'
Optionally filters the command output by object name. The filter uses case-insensitive pattern matching, with support for SQL wildcard characters (% and _).
For example, the following patterns return the same results:
... LIKE '%testing%' ...
... LIKE '%TESTING%' ...
. Default: No value (no filtering is applied to the output).
[ IN ... ]
Optionally specifies the scope of the command. Specify one of the following:
ACCOUNT
Returns records for the entire account.
DATABASE, . DATABASE db_name
Returns records for the current database in use or for a specified database (db_name).
If you specify DATABASE without db_name and no database is in use, the keyword has no effect on the output.
Note
Using SHOW commands without an IN clause in a database context can result in fewer than expected results.
Objects with the same name are only displayed once if no IN clause is used. For example, if you have table t1 in schema1 and table t1 in schema2, and they are both in scope of the database context you’ve specified (that is, the database you’ve selected is the parent of schema1 and schema2), then SHOW TABLES only displays one of the t1 tables.
SCHEMA, . SCHEMA schema_name
Returns records for the current schema in use or a specified schema (schema_name).
SCHEMA is optional if a database is in use or if you specify the fully qualified schema_name (for example, db.schema).
If no database is in use, specifying SCHEMA has no effect on the output.
Default: Depends on whether the session currently has a database in use:
Database: DATABASE is the default (that is, the command returns the objects you have privileges to view in the database).
No database: ACCOUNT is the default (that is, the command returns the objects you have privileges to view in your account).
LIMIT rows
Optionally limits the maximum number of rows returned. The actual number of rows returned might be less than the specified limit. For example, the number of existing objects is less than the specified limit.
Default: No value (no limit is applied to the output).
The command output provides Git repository clone 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).
USAGE
Schema
The USAGE privilege on the parent database and schema are required to perform operations on any object in a schema.
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¶The command doesn’t require a running warehouse to execute.
The command only returns objects for which the current user’s current role has been granted at least one access privilege.
The MANAGE GRANTS access privilege implicitly allows its holder to see every object in the account. By default, only the account administrator (users with the ACCOUNTADMIN role) and security administrator (users with the SECURITYADMIN role) have the MANAGE GRANTS privilege.
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 lists repositories in the current schema.
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.EXTENSIONS_SECRET | ACCOUNTADMIN | ROLE | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | 2023-06-28 08:46:10.886 -0700 | SNOWFLAKE_AI | MY_DB | MAIN | https://github.com/my-account/snowflake-AI.git | GIT_API_INTEGRATION | MY_DB.MAIN.AI_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