SHOW IMAGE REPOSITORIES¶
Lists the image repositories for which you have access privileges.
You can use this command to list the repositories in the current database and schema for the session, a specified database or schema, or your entire account.
- See also:
Syntax¶
SHOW IMAGE REPOSITORIES [ LIKE '<pattern>' ]
[ IN
{
ACCOUNT |
DATABASE |
DATABASE <database_name> |
SCHEMA |
SCHEMA <schema_name> |
<schema_name>
}
]
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
withoutdb_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 tablet1
inschema1
and tablet1
inschema2
, and they are both in scope of the database context you’ve specified (that is, the database you’ve selected is the parent ofschema1
andschema2
), then SHOW TABLES only displays one of thet1
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 qualifiedschema_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).
Access control requirements¶
Any of the following repository privileges grants the permission to see repositories in the SHOW IMAGE REPOSITORIES output. If you don’t have any of these privileges, SHOW IMAGE REPOSITORIES will return an empty result.
Privilege |
Object |
Notes |
---|---|---|
READ |
Image repository |
To pull an image from a repository, the role requires this permission. |
WRITE |
Image repository |
To push an image to a repository, the role requires this permission. |
OWNERSHIP |
Image repository |
To create a repository, the role requires this permission. |
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.
Output¶
The command output provides repository properties and metadata in the following columns:
Column |
Description |
---|---|
|
Date and time when the repository was created. |
|
Database in which the repository was created. |
|
Schema in which the repository was created. |
|
URL of the image repository. You need this URL to push (for example, |
|
Role that owns the repository. |
|
The type of role that owns the object; either ROLE or DATABASE_ROLE. |
|
Description for the repository. |
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 RESULT_SCAN function, which treats the output as a table that can be queried.
The command returns a maximum of ten thousand records for the specified object type, as dictated by the access privileges for the role used to execute the command. Any records above the ten thousand records limit aren’t returned, even with a filter applied.
To view results for which more than ten thousand records exist, query the corresponding view (if one exists) in the Snowflake Information Schema.
Examples¶
The following two examples list repositories in the current database and current schema:
SHOW IMAGE REPOSITORIES;
SHOW IMAGE REPOSITORIES IN SCHEMA;
The following example lists repositories in the current database and the specified schema:
SHOW IMAGE REPOSITORIES IN SCHEMA sc1;
The following example lists repositories in the current database and all schemas:
SHOW IMAGE REPOSITORIES IN DATABASE;
The following example lists repositories in the specified database and all schemas:
SHOW IMAGE REPOSITORIES IN DATABASE db1;
The following example lists repositories in the current account (all databases and all schemas):
SHOW IMAGE REPOSITORIES IN ACCOUNT;
Sample output:
+-------------------------------+---------------------+---------------+-------------+-----------------------------------------------------------------------------------------------------------------+-----------+-----------------+---------+
| created_on | name | database_name | schema_name | repository_url | owner | owner_role_type | comment |
|-------------------------------+---------------------+---------------+-------------+-----------------------------------------------------------------------------------------------------------------+-----------+-----------------+---------|
| 2023-05-09 14:27:19.459 -0700 | TUTORIAL_REPOSITORY | TUTORIAL_DB | DATA_SCHEMA | orgname-acctname.registry.snowflakecomputing.cn/tutorial_db/data_schema/tutorial_repository | TEST_ROLE | ROLE | |
+-------------------------------+---------------------+---------------+-------------+-----------------------------------------------------------------------------------------------------------------+-----------+-----------------+---------+