ALTER ORGANIZATION PROFILEΒΆ
Modifies the properties of an organization profile.
- See also:
CREATE ORGANIZATION PROFILE, DESCRIBE AVAILABLE ORGANIZATION PROFILE, DESCRIBE ORGANIZATION PROFILE, DROP ORGANIZATION PROFILE, SHOW AVAILABLE ORGANIZATION PROFILES, SHOW ORGANIZATION PROFILES, SHOW VERSIONS IN ORGANIZATION PROFILE
SyntaxΒΆ
ALTER ORGANIZATION PROFILE [ IF EXISTS ] <name> RENAME TO <new_name>
ALTER ORGANIZATION PROFILE [ IF EXISTS ] <name> PUBLISH
ALTER ORGANIZATION PROFILE <name> ADD VERSION [ [ IF NOT EXISTS ] <version_alias_name> ]
FROM @<yaml_manifest_stage_location>
ALTER ORGANIZATION PROFILE <name> ADD LIVE VERSION [ [ IF NOT EXISTS ] <version_alias_name> ]
FROM LAST
ALTER ORGANIZATION PROFILE <name> COMMIT
ALTER ORGANIZATION PROFILE <name> ABORT
ParametersΒΆ
name
Specifies the identifier (name) for the organization profile being altered. Organization profile names can only contain uppercase characters or numbers, and they must start with an uppercase character.
RENAME TO new_name
Changes the name of the organization profile to
new_name
. The new identifier must be unique within the current organization. The identifier must conform to Snowflake identifier requirements. See Identifier Requirements. Additionally, organization profile names can only contain uppercase characters or numbers, and they must start with an uppercase character.Note
An organization profile with the same name cannot already exist in the organization; otherwise, the statement returns an error.
PUBLISH
Makes a previously undiscoverable organization profile discoverable.
ADD VERSION [ [ IF NOT EXISTS ] version_alias_name ]
Specifies the unique version identifier for the version being added. If
version_alias_name
isnβt specified, an alias isnβt created. If the identifier contains spaces, special characters, or mixed-case characters, the entire identifier must be enclosed in double quotes. Identifiers enclosed in double quotes are also case sensitive. The FIRST, LAST, DEFAULT, and LIVE keywords are reserved as version shortcuts and canβt be used. The unique version identifier canβt start with βversion$β and canβt contain slashes ( / ). For information about identifier syntax, see Identifier Requirements.ADD LIVE VERSION [ [ IF NOT EXISTS ] version_alias_name ]
Adds a new live editable version with the specified name from the last committed version.
version_alias_name
is optional and if it isnβt specified, an alias isnβt created. If the identifier contains spaces, special characters, or mixed-case characters, the entire identifier must be enclosed in double quotes. Identifiers enclosed in double quotes are also case sensitive. The FIRST, LAST, DEFAULT, and LIVE keywords are reserved as version shortcuts and canβt be used. The unique version identifier canβt start with βversion$β and canβt contain slashes ( / ). For information about identifier syntax, see Identifier Requirements.Changes made to the files in a live version are not applied to the organization profile until the live version is committed. The properties of an organization profile remain unchanged until the live version is committed.
FROM 'yaml_manifest_stage_location'
Specifies the external, internal, or repository stage YAML format manifest stage location.
COMMIT
Commits the changes in the organization profile. The live version being committed must contain a valid organization profile manifest file.
ABORT
Discards the changes in the organization profile.
Access control requirementsΒΆ
A role used to execute this SQL command must have either of the following privileges at a minimum:
Privilege |
Object |
Notes |
---|---|---|
OWNERSHIP or MODIFY |
Organization profile |
To create 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ΒΆ
Organization profiles can be renamed only when they are in draft state.
When setting the live version of the YAML format manifest for an organization profile, you must use COMMIT to apply the changes, or ABORT to discard the changes. An organization profile can only have one live version at a time.
ExamplesΒΆ
Alter the organization profile MYORGPROFILE to use an updated manifest file:
ALTER ORGANIZATION PROFILE MYORGPROFILE ADD VERSION V2 FROM @STAGE_PATH_WITH_UPDATED_MANIFEST;
Publish the organization profile MYORGPROFILE:
ALTER ORGANIZATION PROFILE MYORGPROFILE PUBLISH;