mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-18 14:56:05 +00:00
gcloud: Wed Nov 20 10:03:22 UTC 2024
This commit is contained in:
parent
a63704a3af
commit
ad2752c6c9
198 changed files with 7874 additions and 336 deletions
|
|
@ -88,19 +88,29 @@ FLAGS
|
|||
|
||||
--ca-certificate=CA_CERTIFICATE
|
||||
x509 PEM-encoded certificate of the CA that signed the database
|
||||
server's certificate. Database Migration Service will use this
|
||||
certificate to verify it's connecting to the correct host. Database
|
||||
Migration Service encrypts the value when storing it.
|
||||
server's certificate. The value for this flag needs to be the content
|
||||
of the certificate file, not the path to the file. For example, on a
|
||||
Linux machine you can use command substitution:
|
||||
<code>--ca-certificate=$(</path/to/certificate_file.pem)</code>.
|
||||
Database Migration Service will use this certificate to verify it's
|
||||
connecting to the correct host. Database Migration Service encrypts the
|
||||
value when storing it.
|
||||
|
||||
--client-certificate=CLIENT_CERTIFICATE
|
||||
x509 PEM-encoded certificate that will be used by the replica to
|
||||
authenticate against the database server. Database Migration Service
|
||||
encrypts the value when storing it.
|
||||
authenticate against the database server. The value for this flag needs
|
||||
to be the content of the certificate file, not the path to the file.
|
||||
For example, on a Linux machine you can use command substitution:
|
||||
<code>--ca-certificate=$(</path/to/certificate_file.pem)</code>.
|
||||
Database Migration Service encrypts the value when storing it.
|
||||
|
||||
--private-key=PRIVATE_KEY
|
||||
Unencrypted PKCS#1 or PKCS#8 PEM-encoded private key associated with
|
||||
the Client Certificate. Database Migration Service encrypts the value
|
||||
when storing it.
|
||||
the Client Certificate. The value for this flag needs to be the content
|
||||
of the certificate file, not the path to the file. For example, on a
|
||||
Linux machine you can use command substitution:
|
||||
<code>--ca-certificate=$(</path/to/certificate_file.pem)</code>.
|
||||
Database Migration Service encrypts the value when storing it.
|
||||
|
||||
--host=HOST
|
||||
IP or hostname of the database. When --psc-service-attachment is also
|
||||
|
|
|
|||
|
|
@ -93,9 +93,13 @@ OPTIONAL FLAGS
|
|||
|
||||
--ca-certificate=CA_CERTIFICATE
|
||||
x509 PEM-encoded certificate of the CA that signed the database
|
||||
server's certificate. Database Migration Service will use this
|
||||
certificate to verify it's connecting to the correct host. Database
|
||||
Migration Service encrypts the value when storing it.
|
||||
server's certificate. The value for this flag needs to be the content
|
||||
of the certificate file, not the path to the file. For example, on a
|
||||
Linux machine you can use command substitution:
|
||||
<code>--ca-certificate=$(</path/to/certificate_file.pem)</code>.
|
||||
Database Migration Service will use this certificate to verify it's
|
||||
connecting to the correct host. Database Migration Service encrypts the
|
||||
value when storing it.
|
||||
|
||||
--display-name=DISPLAY_NAME
|
||||
A user-friendly name for the connection profile. The display name can
|
||||
|
|
|
|||
|
|
@ -91,19 +91,29 @@ FLAGS
|
|||
|
||||
--ca-certificate=CA_CERTIFICATE
|
||||
x509 PEM-encoded certificate of the CA that signed the database
|
||||
server's certificate. Database Migration Service will use this
|
||||
certificate to verify it's connecting to the correct host. Database
|
||||
Migration Service encrypts the value when storing it.
|
||||
server's certificate. The value for this flag needs to be the content
|
||||
of the certificate file, not the path to the file. For example, on a
|
||||
Linux machine you can use command substitution:
|
||||
<code>--ca-certificate=$(</path/to/certificate_file.pem)</code>.
|
||||
Database Migration Service will use this certificate to verify it's
|
||||
connecting to the correct host. Database Migration Service encrypts the
|
||||
value when storing it.
|
||||
|
||||
--client-certificate=CLIENT_CERTIFICATE
|
||||
x509 PEM-encoded certificate that will be used by the replica to
|
||||
authenticate against the database server. Database Migration Service
|
||||
encrypts the value when storing it.
|
||||
authenticate against the database server. The value for this flag needs
|
||||
to be the content of the certificate file, not the path to the file.
|
||||
For example, on a Linux machine you can use command substitution:
|
||||
<code>--ca-certificate=$(</path/to/certificate_file.pem)</code>.
|
||||
Database Migration Service encrypts the value when storing it.
|
||||
|
||||
--private-key=PRIVATE_KEY
|
||||
Unencrypted PKCS#1 or PKCS#8 PEM-encoded private key associated with
|
||||
the Client Certificate. Database Migration Service encrypts the value
|
||||
when storing it.
|
||||
the Client Certificate. The value for this flag needs to be the content
|
||||
of the certificate file, not the path to the file. For example, on a
|
||||
Linux machine you can use command substitution:
|
||||
<code>--ca-certificate=$(</path/to/certificate_file.pem)</code>.
|
||||
Database Migration Service encrypts the value when storing it.
|
||||
|
||||
--host=HOST
|
||||
IP or hostname of the database. When --psc-service-attachment is also
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue