2022-03-01 04:29:52 +00:00
|
|
|
NAME
|
|
|
|
|
gcloud alpha sql users create - creates a user in a given instance
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
|
gcloud alpha sql users create USERNAME --instance=INSTANCE, -i INSTANCE
|
2026-02-11 11:28:25 +00:00
|
|
|
[--async] [--database-roles=[ROLE,...]] [--host=HOST]
|
|
|
|
|
[--password=PASSWORD]
|
2022-03-01 04:29:52 +00:00
|
|
|
[--password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS]
|
|
|
|
|
[--[no-]password-policy-enable-failed-attempts-check]
|
2022-07-13 09:59:38 +00:00
|
|
|
[--[no-]password-policy-enable-password-verification]
|
2022-03-01 04:29:52 +00:00
|
|
|
[--password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION]
|
|
|
|
|
[--type=TYPE] [GCLOUD_WIDE_FLAG ...]
|
|
|
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
|
(ALPHA) Creates a user in a given instance with specified username, host,
|
|
|
|
|
type, and password.
|
|
|
|
|
|
|
|
|
|
POSITIONAL ARGUMENTS
|
|
|
|
|
USERNAME
|
|
|
|
|
Cloud SQL username.
|
|
|
|
|
|
|
|
|
|
REQUIRED FLAGS
|
|
|
|
|
--instance=INSTANCE, -i INSTANCE
|
|
|
|
|
Cloud SQL instance ID.
|
|
|
|
|
|
|
|
|
|
OPTIONAL FLAGS
|
|
|
|
|
--async
|
|
|
|
|
Return immediately, without waiting for the operation in progress to
|
|
|
|
|
complete.
|
|
|
|
|
|
2026-02-11 11:28:25 +00:00
|
|
|
--database-roles=[ROLE,...]
|
|
|
|
|
A comma-separated list of database roles to be assigned to the user.
|
|
|
|
|
This option is only available for MySQL and PostgreSQL instances. You
|
|
|
|
|
can include predefined Cloud SQL roles, like cloudsqlsuperuser, or your
|
|
|
|
|
own custom roles. Custom roles must be created in the database before
|
|
|
|
|
you can assign them. You can create roles using the CREATE ROLE
|
|
|
|
|
statement for both MySQL and PostgreSQL.
|
|
|
|
|
|
2022-03-01 04:29:52 +00:00
|
|
|
--host=HOST
|
2023-01-25 10:09:52 +00:00
|
|
|
Cloud SQL user's hostname expressed as a specific IP address or address
|
|
|
|
|
range. % denotes an unrestricted hostname. Applicable flag for MySQL
|
|
|
|
|
instances; ignored for all other engines. Note, if you connect to your
|
|
|
|
|
instance using IP addresses, you must add your client IP address as an
|
|
|
|
|
authorized address, even if your hostname is unrestricted. For more
|
|
|
|
|
information, see Configure IP
|
|
|
|
|
(https://cloud.google.com/sql/docs/mysql/configure-ip).
|
2022-03-01 04:29:52 +00:00
|
|
|
|
|
|
|
|
--password=PASSWORD
|
|
|
|
|
Cloud SQL user's password.
|
|
|
|
|
|
|
|
|
|
--password-policy-allowed-failed-attempts=PASSWORD_POLICY_ALLOWED_FAILED_ATTEMPTS
|
|
|
|
|
Number of failed login attempts allowed before a user is locked out.
|
|
|
|
|
|
|
|
|
|
--[no-]password-policy-enable-failed-attempts-check
|
2025-06-14 05:31:37 +00:00
|
|
|
Enables the failed login attempts check if set to true. Use
|
2022-03-01 04:29:52 +00:00
|
|
|
--password-policy-enable-failed-attempts-check to enable and
|
|
|
|
|
--no-password-policy-enable-failed-attempts-check to disable.
|
|
|
|
|
|
2022-07-13 09:59:38 +00:00
|
|
|
--[no-]password-policy-enable-password-verification
|
2025-06-14 05:31:37 +00:00
|
|
|
The current password must be specified when altering the password. Use
|
2022-07-13 09:59:38 +00:00
|
|
|
--password-policy-enable-password-verification to enable and
|
|
|
|
|
--no-password-policy-enable-password-verification to disable.
|
|
|
|
|
|
2022-03-01 04:29:52 +00:00
|
|
|
--password-policy-password-expiration-duration=PASSWORD_POLICY_PASSWORD_EXPIRATION_DURATION
|
2022-07-13 09:59:38 +00:00
|
|
|
Expiration duration after a password is updated, for example, 2d for 2
|
|
|
|
|
days. See gcloud topic datetimes for information on duration formats.
|
2022-03-01 04:29:52 +00:00
|
|
|
|
|
|
|
|
--type=TYPE
|
|
|
|
|
Cloud SQL user's type. It determines the method to authenticate the
|
|
|
|
|
user during login. See the list of user types at
|
|
|
|
|
https://cloud.google.com/sql/docs/postgres/admin-api/rest/v1beta4/SqlUserType
|
|
|
|
|
|
|
|
|
|
GCLOUD WIDE FLAGS
|
|
|
|
|
These flags are available to all commands: --access-token-file, --account,
|
|
|
|
|
--billing-project, --configuration, --flags-file, --flatten, --format,
|
|
|
|
|
--help, --impersonate-service-account, --log-http, --project, --quiet,
|
|
|
|
|
--trace-token, --user-output-enabled, --verbosity.
|
|
|
|
|
|
|
|
|
|
Run $ gcloud help for details.
|
|
|
|
|
|
|
|
|
|
NOTES
|
|
|
|
|
This command is currently in alpha and might change without notice. If this
|
|
|
|
|
command fails with API permission errors despite specifying the correct
|
|
|
|
|
project, you might be trying to access an API with an invitation-only early
|
|
|
|
|
access allowlist. These variants are also available:
|
|
|
|
|
|
|
|
|
|
$ gcloud sql users create
|
|
|
|
|
|
|
|
|
|
$ gcloud beta sql users create
|
|
|
|
|
|