oci-cli 3.64.0__py3-none-any.whl → 3.64.1__py3-none-any.whl
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- oci_cli/help_text_producer/data_files/text/cmdref/data-safe/security-assessment/list-finding-analytics.txt +14 -0
- oci_cli/help_text_producer/data_files/text/cmdref/data-safe/security-assessment/list-findings.txt +8 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/pluggable-database/create-local-clone.txt +4 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/pluggable-database/create-remote-clone.txt +4 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/pluggable-database/create-snapshot.txt +157 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/pluggable-database/delete-snapshot.txt +129 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/pluggable-database/get-snapshot.txt +92 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/pluggable-database/list-snapshots.txt +145 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/pluggable-database.txt +8 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db.txt +8 -0
- oci_cli/help_text_producer/data_files/text/cmdref/delegate-access-control/work-request/{work-request-log/list.txt → work-request-log-entry/list-work-request-logs.txt} +5 -5
- oci_cli/help_text_producer/data_files/text/cmdref/delegate-access-control/work-request/{work-request-log.txt → work-request-log-entry.txt} +3 -3
- oci_cli/help_text_producer/data_files/text/cmdref/delegate-access-control/work-request.txt +2 -2
- oci_cli/help_text_producer/data_files/text/cmdref/delegate-access-control.txt +2 -2
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai-inference/chat-result/chat-cohere-chat-request.txt +3 -1
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai-inference/chat-result/chat-generic-chat-request.txt +83 -3
- oci_cli/help_text_producer/data_files/text/cmdref/governance-rules-control-plane/work-request/work-request-error/{list.txt → list-errors.txt} +5 -5
- oci_cli/help_text_producer/data_files/text/cmdref/governance-rules-control-plane/work-request/work-request-error.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/governance-rules-control-plane/work-request/work-request-log-entry/{list-work-request-logs.txt → list-logs.txt} +5 -5
- oci_cli/help_text_producer/data_files/text/cmdref/governance-rules-control-plane/work-request/work-request-log-entry.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/governance-rules-control-plane/work-request.txt +2 -2
- oci_cli/help_text_producer/data_files/text/cmdref/governance-rules-control-plane.txt +2 -2
- oci_cli/help_text_producer/data_files/text/cmdref/lfs/lustre-file-system.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/lfs.txt +2 -1
- oci_cli/help_text_producer/data_files/text/cmdref/network/ipv6/create.txt +4 -0
- oci_cli/help_text_producer/data_files/text/cmdref/network/vnic/assign-ipv6.txt +4 -0
- oci_cli/help_text_producer/data_files/text/cmdref/support/incident/create.txt +6 -6
- oci_cli/help_text_producer/data_files/text/cmdref/support/incident/get.txt +2 -2
- oci_cli/help_text_producer/data_files/text/cmdref/support/incident/list.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/support/incident/update.txt +4 -4
- oci_cli/help_text_producer/data_files/text/cmdref/support/incident-resource-type/list.txt +3 -3
- oci_cli/help_text_producer/data_files/text/cmdref/support/validation-response/validate-user.txt +1 -1
- oci_cli/version.py +1 -1
- {oci_cli-3.64.0.dist-info → oci_cli-3.64.1.dist-info}/METADATA +2 -2
- {oci_cli-3.64.0.dist-info → oci_cli-3.64.1.dist-info}/RECORD +46 -42
- services/core/src/oci_cli_virtual_network/generated/virtualnetwork_cli.py +5 -1
- services/core/src/oci_cli_virtual_network/virtualnetwork_cli_extended.py +5 -1
- services/data_safe/src/oci_cli_data_safe/generated/datasafe_cli.py +12 -2
- services/database/src/oci_cli_database/database_cli_extended.py +53 -2
- services/database/src/oci_cli_database/generated/database_cli.py +222 -2
- services/generative_ai_inference/src/oci_cli_generative_ai_inference/generated/generativeaiinference_cli.py +39 -5
- {oci_cli-3.64.0.dist-info → oci_cli-3.64.1.dist-info}/LICENSE.txt +0 -0
- {oci_cli-3.64.0.dist-info → oci_cli-3.64.1.dist-info}/THIRD_PARTY_LICENSES.txt +0 -0
- {oci_cli-3.64.0.dist-info → oci_cli-3.64.1.dist-info}/WHEEL +0 -0
- {oci_cli-3.64.0.dist-info → oci_cli-3.64.1.dist-info}/entry_points.txt +0 -0
- {oci_cli-3.64.0.dist-info → oci_cli-3.64.1.dist-info}/top_level.txt +0 -0
|
@@ -158,6 +158,20 @@ Pagination.
|
|
|
158
158
|
When fetching results, the number of results to fetch per call. Only
|
|
159
159
|
valid when used with "--all" or "--limit", and ignored otherwise.
|
|
160
160
|
|
|
161
|
+
--scim-query [text]
|
|
162
|
+
|
|
163
|
+
The scimQuery query parameter accepts filter expressions that use the
|
|
164
|
+
syntax described in Section 3.2.2.2 of the System for Cross-Domain
|
|
165
|
+
Identity Management (SCIM) specification, which is available at
|
|
166
|
+
RFC3339. In SCIM filtering expressions, text, date, and time values
|
|
167
|
+
must be enclosed in quotation marks, with date and time values using
|
|
168
|
+
ISO-8601 format. (Numeric and boolean values should not be quoted.)
|
|
169
|
+
|
|
170
|
+
**Example:** | scimQuery=(severity eq ‘high’) scimQuery=(category eq
|
|
171
|
+
“Users”) and (reference eq ‘CIS’)
|
|
172
|
+
|
|
173
|
+
Supported fields: severity reference title category
|
|
174
|
+
|
|
161
175
|
--severity [text]
|
|
162
176
|
|
|
163
177
|
A filter to return only findings of a particular risk level.
|
oci_cli/help_text_producer/data_files/text/cmdref/data-safe/security-assessment/list-findings.txt
CHANGED
|
@@ -198,6 +198,14 @@ Accepted values are:
|
|
|
198
198
|
|
|
199
199
|
category, findingKey, severity
|
|
200
200
|
|
|
201
|
+
--sort-order [text]
|
|
202
|
+
|
|
203
|
+
The sort order to use, either ascending (ASC) or descending (DESC).
|
|
204
|
+
|
|
205
|
+
Accepted values are:
|
|
206
|
+
|
|
207
|
+
ASC, DESC
|
|
208
|
+
|
|
201
209
|
--target-id [text]
|
|
202
210
|
|
|
203
211
|
A filter to return only items related to a specific target OCID.
|
oci_cli/help_text_producer/data_files/text/cmdref/db/pluggable-database/create-local-clone.txt
CHANGED
|
@@ -140,6 +140,10 @@ characters and contain at least two uppercase, two lowercase, two
|
|
|
140
140
|
numbers, and two special characters. The special characters must be _,
|
|
141
141
|
#, or -.
|
|
142
142
|
|
|
143
|
+
--source-pdb-snapshot-id [text]
|
|
144
|
+
|
|
145
|
+
The OCID of the Source Pluggable Database Snapshot id.
|
|
146
|
+
|
|
143
147
|
--tde-wallet-password [text]
|
|
144
148
|
|
|
145
149
|
The existing TDE wallet password of the CDB.
|
oci_cli/help_text_producer/data_files/text/cmdref/db/pluggable-database/create-remote-clone.txt
CHANGED
|
@@ -158,6 +158,10 @@ characters and contain at least two uppercase, two lowercase, two
|
|
|
158
158
|
numbers, and two special characters. The special characters must be _,
|
|
159
159
|
#, or -.
|
|
160
160
|
|
|
161
|
+
--source-pdb-snapshot-id [text]
|
|
162
|
+
|
|
163
|
+
The OCID of the Source Pluggable Database Snapshot id.
|
|
164
|
+
|
|
161
165
|
--tde-wallet-password [text]
|
|
162
166
|
|
|
163
167
|
The existing TDE wallet password of the CDB.
|
|
@@ -0,0 +1,157 @@
|
|
|
1
|
+
"create-snapshot"
|
|
2
|
+
*****************
|
|
3
|
+
|
|
4
|
+
* Description
|
|
5
|
+
|
|
6
|
+
* Usage
|
|
7
|
+
|
|
8
|
+
* Required Parameters
|
|
9
|
+
|
|
10
|
+
* Optional Parameters
|
|
11
|
+
|
|
12
|
+
* Global Parameters
|
|
13
|
+
|
|
14
|
+
* Example using required parameter
|
|
15
|
+
|
|
16
|
+
|
|
17
|
+
Description
|
|
18
|
+
===========
|
|
19
|
+
|
|
20
|
+
Creates a Pluggable Database Snapshot
|
|
21
|
+
|
|
22
|
+
|
|
23
|
+
Usage
|
|
24
|
+
=====
|
|
25
|
+
|
|
26
|
+
oci db pluggable-database create-snapshot [OPTIONS]
|
|
27
|
+
|
|
28
|
+
|
|
29
|
+
Required Parameters
|
|
30
|
+
===================
|
|
31
|
+
|
|
32
|
+
--name [text]
|
|
33
|
+
|
|
34
|
+
The user-friendly name for the Database Snapshot. The name should be
|
|
35
|
+
unique.
|
|
36
|
+
|
|
37
|
+
--pluggable-database-id [text]
|
|
38
|
+
|
|
39
|
+
The OCID of the Exadata Pluggable Database.
|
|
40
|
+
|
|
41
|
+
|
|
42
|
+
Optional Parameters
|
|
43
|
+
===================
|
|
44
|
+
|
|
45
|
+
--defined-tags [complex type]
|
|
46
|
+
|
|
47
|
+
Defined tags for this resource. Each key is predefined and scoped to a
|
|
48
|
+
namespace. For more information, see Resource Tags. This is a complex
|
|
49
|
+
type whose value must be valid JSON. The value can be provided as a
|
|
50
|
+
string on the command line or passed in as a file using the
|
|
51
|
+
file://path/to/file syntax.
|
|
52
|
+
|
|
53
|
+
The "--generate-param-json-input" option can be used to generate an
|
|
54
|
+
example of the JSON which must be provided. We recommend storing this
|
|
55
|
+
example in a file, modifying it as needed and then passing it back in
|
|
56
|
+
via the file:// syntax.
|
|
57
|
+
|
|
58
|
+
--freeform-tags [complex type]
|
|
59
|
+
|
|
60
|
+
Free-form tags for this resource. Each tag is a simple key-value pair
|
|
61
|
+
with no predefined name, type, or namespace. For more information, see
|
|
62
|
+
Resource Tags.
|
|
63
|
+
|
|
64
|
+
Example:
|
|
65
|
+
|
|
66
|
+
{"Department": "Finance"}
|
|
67
|
+
|
|
68
|
+
This is a complex type whose value must be valid JSON. The value can
|
|
69
|
+
be provided as a string on the command line or passed in as a file
|
|
70
|
+
using the file://path/to/file syntax.
|
|
71
|
+
|
|
72
|
+
The "--generate-param-json-input" option can be used to generate an
|
|
73
|
+
example of the JSON which must be provided. We recommend storing this
|
|
74
|
+
example in a file, modifying it as needed and then passing it back in
|
|
75
|
+
via the file:// syntax.
|
|
76
|
+
|
|
77
|
+
--from-json [text]
|
|
78
|
+
|
|
79
|
+
Provide input to this command as a JSON document from a file using the
|
|
80
|
+
file://path-to/file syntax.
|
|
81
|
+
|
|
82
|
+
The "--generate-full-command-json-input" option can be used to
|
|
83
|
+
generate a sample json file to be used with this command option. The
|
|
84
|
+
key names are pre-populated and match the command option names
|
|
85
|
+
(converted to camelCase format, e.g. compartment-id –> compartmentId),
|
|
86
|
+
while the values of the keys need to be populated by the user before
|
|
87
|
+
using the sample file as an input to this command. For any command
|
|
88
|
+
option that accepts multiple values, the value of the key can be a
|
|
89
|
+
JSON array.
|
|
90
|
+
|
|
91
|
+
Options can still be provided on the command line. If an option exists
|
|
92
|
+
in both the JSON document and the command line then the command line
|
|
93
|
+
specified value will be used.
|
|
94
|
+
|
|
95
|
+
For examples on usage of this option, please see our “using CLI with
|
|
96
|
+
advanced JSON options” link: https://docs.cloud.oracle.com/iaas/Conte
|
|
97
|
+
nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
|
|
98
|
+
|
|
99
|
+
--max-wait-seconds [integer]
|
|
100
|
+
|
|
101
|
+
The maximum time to wait for the resource to reach the lifecycle state
|
|
102
|
+
defined by "--wait-for-state". Defaults to 1200 seconds.
|
|
103
|
+
|
|
104
|
+
--wait-for-state [text]
|
|
105
|
+
|
|
106
|
+
This operation creates, modifies or deletes a resource that has a
|
|
107
|
+
defined lifecycle state. Specify this option to perform the action and
|
|
108
|
+
then wait until the resource reaches a given lifecycle state. Multiple
|
|
109
|
+
states can be specified, returning on the first state. For example, "
|
|
110
|
+
--wait-for-state" SUCCEEDED "--wait-for-state" FAILED would return on
|
|
111
|
+
whichever lifecycle state is reached first. If timeout is reached, a
|
|
112
|
+
return code of 2 is returned. For any other error, a return code of 1
|
|
113
|
+
is returned.
|
|
114
|
+
|
|
115
|
+
Accepted values are:
|
|
116
|
+
|
|
117
|
+
AVAILABLE, CREATING, FAILED, TERMINATED, TERMINATING
|
|
118
|
+
|
|
119
|
+
--wait-interval-seconds [integer]
|
|
120
|
+
|
|
121
|
+
Check every "--wait-interval-seconds" to see whether the resource has
|
|
122
|
+
reached the lifecycle state defined by "--wait-for-state". Defaults to
|
|
123
|
+
30 seconds.
|
|
124
|
+
|
|
125
|
+
|
|
126
|
+
Global Parameters
|
|
127
|
+
=================
|
|
128
|
+
|
|
129
|
+
Use "oci --help" for help on global parameters.
|
|
130
|
+
|
|
131
|
+
"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
|
|
132
|
+
cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
|
|
133
|
+
defaults-file", "--endpoint", "--generate-full-command-json-input", "
|
|
134
|
+
--generate-param-json-input", "--help", "--latest-version", "--max-
|
|
135
|
+
retries", "--no-retry", "--opc-client-request-id", "--opc-request-id",
|
|
136
|
+
"--output", "--profile", "--proxy", "--query", "--raw-output", "--
|
|
137
|
+
read-timeout", "--realm-specific-endpoint", "--region", "--release-
|
|
138
|
+
info", "--request-id", "--version", "-?", "-d", "-h", "-i", "-v"
|
|
139
|
+
|
|
140
|
+
|
|
141
|
+
Example using required parameter
|
|
142
|
+
================================
|
|
143
|
+
|
|
144
|
+
Copy the following CLI commands into a file named example.sh. Run the
|
|
145
|
+
command by typing “bash example.sh” and replacing the example
|
|
146
|
+
parameters with your own.
|
|
147
|
+
|
|
148
|
+
Please note this sample will only work in the POSIX-compliant bash-
|
|
149
|
+
like shell. You need to set up the OCI configuration and appropriate
|
|
150
|
+
security policies before trying the examples.
|
|
151
|
+
|
|
152
|
+
export container_database_id=<substitute-value-of-container_database_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/pluggable-database/create.html#cmdoption-container-database-id
|
|
153
|
+
export pdb_name=<substitute-value-of-pdb_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/pluggable-database/create.html#cmdoption-pdb-name
|
|
154
|
+
|
|
155
|
+
pluggable_database_id=$(oci db pluggable-database create --container-database-id $container_database_id --pdb-name $pdb_name --query data.id --raw-output)
|
|
156
|
+
|
|
157
|
+
oci db pluggable-database create-snapshot --name $name --pluggable-database-id $pluggable_database_id
|
|
@@ -0,0 +1,129 @@
|
|
|
1
|
+
"delete-snapshot"
|
|
2
|
+
*****************
|
|
3
|
+
|
|
4
|
+
* Description
|
|
5
|
+
|
|
6
|
+
* Usage
|
|
7
|
+
|
|
8
|
+
* Required Parameters
|
|
9
|
+
|
|
10
|
+
* Optional Parameters
|
|
11
|
+
|
|
12
|
+
* Global Parameters
|
|
13
|
+
|
|
14
|
+
* Example using required parameter
|
|
15
|
+
|
|
16
|
+
|
|
17
|
+
Description
|
|
18
|
+
===========
|
|
19
|
+
|
|
20
|
+
Deletes the specified Exadata Pluggable Database Snapshot.
|
|
21
|
+
|
|
22
|
+
|
|
23
|
+
Usage
|
|
24
|
+
=====
|
|
25
|
+
|
|
26
|
+
oci db pluggable-database delete-snapshot [OPTIONS]
|
|
27
|
+
|
|
28
|
+
|
|
29
|
+
Required Parameters
|
|
30
|
+
===================
|
|
31
|
+
|
|
32
|
+
--pdb-snapshot-id [text]
|
|
33
|
+
|
|
34
|
+
The Exadata Pluggable Database Snapshot OCID.
|
|
35
|
+
|
|
36
|
+
|
|
37
|
+
Optional Parameters
|
|
38
|
+
===================
|
|
39
|
+
|
|
40
|
+
--force
|
|
41
|
+
|
|
42
|
+
Perform deletion without prompting for confirmation.
|
|
43
|
+
|
|
44
|
+
--from-json [text]
|
|
45
|
+
|
|
46
|
+
Provide input to this command as a JSON document from a file using the
|
|
47
|
+
file://path-to/file syntax.
|
|
48
|
+
|
|
49
|
+
The "--generate-full-command-json-input" option can be used to
|
|
50
|
+
generate a sample json file to be used with this command option. The
|
|
51
|
+
key names are pre-populated and match the command option names
|
|
52
|
+
(converted to camelCase format, e.g. compartment-id –> compartmentId),
|
|
53
|
+
while the values of the keys need to be populated by the user before
|
|
54
|
+
using the sample file as an input to this command. For any command
|
|
55
|
+
option that accepts multiple values, the value of the key can be a
|
|
56
|
+
JSON array.
|
|
57
|
+
|
|
58
|
+
Options can still be provided on the command line. If an option exists
|
|
59
|
+
in both the JSON document and the command line then the command line
|
|
60
|
+
specified value will be used.
|
|
61
|
+
|
|
62
|
+
For examples on usage of this option, please see our “using CLI with
|
|
63
|
+
advanced JSON options” link: https://docs.cloud.oracle.com/iaas/Conte
|
|
64
|
+
nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
|
|
65
|
+
|
|
66
|
+
--if-match [text]
|
|
67
|
+
|
|
68
|
+
For optimistic concurrency control. In the PUT or DELETE call for a
|
|
69
|
+
resource, set the *if-match* parameter to the value of the etag from a
|
|
70
|
+
previous GET or POST response for that resource. The resource will be
|
|
71
|
+
updated or deleted only if the etag you provide matches the resource’s
|
|
72
|
+
current etag value.
|
|
73
|
+
|
|
74
|
+
--max-wait-seconds [integer]
|
|
75
|
+
|
|
76
|
+
The maximum time to wait for the work request to reach the state
|
|
77
|
+
defined by "--wait-for-state". Defaults to 1200 seconds.
|
|
78
|
+
|
|
79
|
+
--wait-for-state [text]
|
|
80
|
+
|
|
81
|
+
This operation asynchronously creates, modifies or deletes a resource
|
|
82
|
+
and uses a work request to track the progress of the operation.
|
|
83
|
+
Specify this option to perform the action and then wait until the work
|
|
84
|
+
request reaches a certain state. Multiple states can be specified,
|
|
85
|
+
returning on the first state. For example, "--wait-for-state"
|
|
86
|
+
SUCCEEDED "--wait-for-state" FAILED would return on whichever
|
|
87
|
+
lifecycle state is reached first. If timeout is reached, a return code
|
|
88
|
+
of 2 is returned. For any other error, a return code of 1 is returned.
|
|
89
|
+
|
|
90
|
+
Accepted values are:
|
|
91
|
+
|
|
92
|
+
ACCEPTED, FAILED, IN_PROGRESS, SUCCEEDED
|
|
93
|
+
|
|
94
|
+
--wait-interval-seconds [integer]
|
|
95
|
+
|
|
96
|
+
Check every "--wait-interval-seconds" to see whether the work request
|
|
97
|
+
has reached the state defined by "--wait-for-state". Defaults to 30
|
|
98
|
+
seconds.
|
|
99
|
+
|
|
100
|
+
|
|
101
|
+
Global Parameters
|
|
102
|
+
=================
|
|
103
|
+
|
|
104
|
+
Use "oci --help" for help on global parameters.
|
|
105
|
+
|
|
106
|
+
"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
|
|
107
|
+
cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
|
|
108
|
+
defaults-file", "--endpoint", "--generate-full-command-json-input", "
|
|
109
|
+
--generate-param-json-input", "--help", "--latest-version", "--max-
|
|
110
|
+
retries", "--no-retry", "--opc-client-request-id", "--opc-request-id",
|
|
111
|
+
"--output", "--profile", "--proxy", "--query", "--raw-output", "--
|
|
112
|
+
read-timeout", "--realm-specific-endpoint", "--region", "--release-
|
|
113
|
+
info", "--request-id", "--version", "-?", "-d", "-h", "-i", "-v"
|
|
114
|
+
|
|
115
|
+
|
|
116
|
+
Example using required parameter
|
|
117
|
+
================================
|
|
118
|
+
|
|
119
|
+
Copy the following CLI commands into a file named example.sh. Run the
|
|
120
|
+
command by typing “bash example.sh” and replacing the example
|
|
121
|
+
parameters with your own.
|
|
122
|
+
|
|
123
|
+
Please note this sample will only work in the POSIX-compliant bash-
|
|
124
|
+
like shell. You need to set up the OCI configuration and appropriate
|
|
125
|
+
security policies before trying the examples.
|
|
126
|
+
|
|
127
|
+
export pdb_snapshot_id=<substitute-value-of-pdb_snapshot_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/pluggable-database/delete-snapshot.html#cmdoption-pdb-snapshot-id
|
|
128
|
+
|
|
129
|
+
oci db pluggable-database delete-snapshot --pdb-snapshot-id $pdb_snapshot_id
|
|
@@ -0,0 +1,92 @@
|
|
|
1
|
+
"get-snapshot"
|
|
2
|
+
**************
|
|
3
|
+
|
|
4
|
+
* Description
|
|
5
|
+
|
|
6
|
+
* Usage
|
|
7
|
+
|
|
8
|
+
* Required Parameters
|
|
9
|
+
|
|
10
|
+
* Optional Parameters
|
|
11
|
+
|
|
12
|
+
* Global Parameters
|
|
13
|
+
|
|
14
|
+
* Example using required parameter
|
|
15
|
+
|
|
16
|
+
|
|
17
|
+
Description
|
|
18
|
+
===========
|
|
19
|
+
|
|
20
|
+
Gets information about the specified Exadata Pluggable Database
|
|
21
|
+
Snapshot in the specified compartment.
|
|
22
|
+
|
|
23
|
+
|
|
24
|
+
Usage
|
|
25
|
+
=====
|
|
26
|
+
|
|
27
|
+
oci db pluggable-database get-snapshot [OPTIONS]
|
|
28
|
+
|
|
29
|
+
|
|
30
|
+
Required Parameters
|
|
31
|
+
===================
|
|
32
|
+
|
|
33
|
+
--pdb-snapshot-id [text]
|
|
34
|
+
|
|
35
|
+
The Exadata Pluggable Database Snapshot OCID.
|
|
36
|
+
|
|
37
|
+
|
|
38
|
+
Optional Parameters
|
|
39
|
+
===================
|
|
40
|
+
|
|
41
|
+
--from-json [text]
|
|
42
|
+
|
|
43
|
+
Provide input to this command as a JSON document from a file using the
|
|
44
|
+
file://path-to/file syntax.
|
|
45
|
+
|
|
46
|
+
The "--generate-full-command-json-input" option can be used to
|
|
47
|
+
generate a sample json file to be used with this command option. The
|
|
48
|
+
key names are pre-populated and match the command option names
|
|
49
|
+
(converted to camelCase format, e.g. compartment-id –> compartmentId),
|
|
50
|
+
while the values of the keys need to be populated by the user before
|
|
51
|
+
using the sample file as an input to this command. For any command
|
|
52
|
+
option that accepts multiple values, the value of the key can be a
|
|
53
|
+
JSON array.
|
|
54
|
+
|
|
55
|
+
Options can still be provided on the command line. If an option exists
|
|
56
|
+
in both the JSON document and the command line then the command line
|
|
57
|
+
specified value will be used.
|
|
58
|
+
|
|
59
|
+
For examples on usage of this option, please see our “using CLI with
|
|
60
|
+
advanced JSON options” link: https://docs.cloud.oracle.com/iaas/Conte
|
|
61
|
+
nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
|
|
62
|
+
|
|
63
|
+
|
|
64
|
+
Global Parameters
|
|
65
|
+
=================
|
|
66
|
+
|
|
67
|
+
Use "oci --help" for help on global parameters.
|
|
68
|
+
|
|
69
|
+
"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
|
|
70
|
+
cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
|
|
71
|
+
defaults-file", "--endpoint", "--generate-full-command-json-input", "
|
|
72
|
+
--generate-param-json-input", "--help", "--latest-version", "--max-
|
|
73
|
+
retries", "--no-retry", "--opc-client-request-id", "--opc-request-id",
|
|
74
|
+
"--output", "--profile", "--proxy", "--query", "--raw-output", "--
|
|
75
|
+
read-timeout", "--realm-specific-endpoint", "--region", "--release-
|
|
76
|
+
info", "--request-id", "--version", "-?", "-d", "-h", "-i", "-v"
|
|
77
|
+
|
|
78
|
+
|
|
79
|
+
Example using required parameter
|
|
80
|
+
================================
|
|
81
|
+
|
|
82
|
+
Copy the following CLI commands into a file named example.sh. Run the
|
|
83
|
+
command by typing “bash example.sh” and replacing the example
|
|
84
|
+
parameters with your own.
|
|
85
|
+
|
|
86
|
+
Please note this sample will only work in the POSIX-compliant bash-
|
|
87
|
+
like shell. You need to set up the OCI configuration and appropriate
|
|
88
|
+
security policies before trying the examples.
|
|
89
|
+
|
|
90
|
+
export pdb_snapshot_id=<substitute-value-of-pdb_snapshot_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/pluggable-database/get-snapshot.html#cmdoption-pdb-snapshot-id
|
|
91
|
+
|
|
92
|
+
oci db pluggable-database get-snapshot --pdb-snapshot-id $pdb_snapshot_id
|
|
@@ -0,0 +1,145 @@
|
|
|
1
|
+
"list-snapshots"
|
|
2
|
+
****************
|
|
3
|
+
|
|
4
|
+
* Description
|
|
5
|
+
|
|
6
|
+
* Usage
|
|
7
|
+
|
|
8
|
+
* Optional Parameters
|
|
9
|
+
|
|
10
|
+
* Global Parameters
|
|
11
|
+
|
|
12
|
+
* Example using required parameter
|
|
13
|
+
|
|
14
|
+
|
|
15
|
+
Description
|
|
16
|
+
===========
|
|
17
|
+
|
|
18
|
+
Gets a list of the Exadata Pluggable Database Snapshots in the
|
|
19
|
+
specified compartment.
|
|
20
|
+
|
|
21
|
+
|
|
22
|
+
Usage
|
|
23
|
+
=====
|
|
24
|
+
|
|
25
|
+
oci db pluggable-database list-snapshots [OPTIONS]
|
|
26
|
+
|
|
27
|
+
|
|
28
|
+
Optional Parameters
|
|
29
|
+
===================
|
|
30
|
+
|
|
31
|
+
--all
|
|
32
|
+
|
|
33
|
+
Fetches all pages of results. If you provide this option, then you
|
|
34
|
+
cannot provide the "--limit" option.
|
|
35
|
+
|
|
36
|
+
--cluster-id [text]
|
|
37
|
+
|
|
38
|
+
A filter to return only Exadata Database Node Snapshots that match the
|
|
39
|
+
given VM cluster.
|
|
40
|
+
|
|
41
|
+
--compartment-id, -c [text]
|
|
42
|
+
|
|
43
|
+
The compartment OCID.
|
|
44
|
+
|
|
45
|
+
--from-json [text]
|
|
46
|
+
|
|
47
|
+
Provide input to this command as a JSON document from a file using the
|
|
48
|
+
file://path-to/file syntax.
|
|
49
|
+
|
|
50
|
+
The "--generate-full-command-json-input" option can be used to
|
|
51
|
+
generate a sample json file to be used with this command option. The
|
|
52
|
+
key names are pre-populated and match the command option names
|
|
53
|
+
(converted to camelCase format, e.g. compartment-id –> compartmentId),
|
|
54
|
+
while the values of the keys need to be populated by the user before
|
|
55
|
+
using the sample file as an input to this command. For any command
|
|
56
|
+
option that accepts multiple values, the value of the key can be a
|
|
57
|
+
JSON array.
|
|
58
|
+
|
|
59
|
+
Options can still be provided on the command line. If an option exists
|
|
60
|
+
in both the JSON document and the command line then the command line
|
|
61
|
+
specified value will be used.
|
|
62
|
+
|
|
63
|
+
For examples on usage of this option, please see our “using CLI with
|
|
64
|
+
advanced JSON options” link: https://docs.cloud.oracle.com/iaas/Conte
|
|
65
|
+
nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
|
|
66
|
+
|
|
67
|
+
--lifecycle-state [text]
|
|
68
|
+
|
|
69
|
+
A filter to return only Exadata Pluggable Database Snapshots that
|
|
70
|
+
match the given lifecycle state exactly.
|
|
71
|
+
|
|
72
|
+
Accepted values are:
|
|
73
|
+
|
|
74
|
+
AVAILABLE, CREATING, FAILED, TERMINATED, TERMINATING
|
|
75
|
+
|
|
76
|
+
--limit [integer]
|
|
77
|
+
|
|
78
|
+
The maximum number of items to return per page.
|
|
79
|
+
|
|
80
|
+
--name [text]
|
|
81
|
+
|
|
82
|
+
A filter to return only resources that match the entire name given.
|
|
83
|
+
The match is not case sensitive.
|
|
84
|
+
|
|
85
|
+
--page [text]
|
|
86
|
+
|
|
87
|
+
The pagination token to continue listing from.
|
|
88
|
+
|
|
89
|
+
--page-size [integer]
|
|
90
|
+
|
|
91
|
+
When fetching results, the number of results to fetch per call. Only
|
|
92
|
+
valid when used with "--all" or "--limit", and ignored otherwise.
|
|
93
|
+
|
|
94
|
+
--pluggable-database-id [text]
|
|
95
|
+
|
|
96
|
+
A filter to return only Exadata Pluggable Database Snapshots that
|
|
97
|
+
match the given database OCID.
|
|
98
|
+
|
|
99
|
+
--sort-by [text]
|
|
100
|
+
|
|
101
|
+
The field to sort by. You can provide one sort order (*sortOrder*).
|
|
102
|
+
Default order for TIMECREATED is descending. Default order for NAME is
|
|
103
|
+
ascending. The NAME sort order is case sensitive.
|
|
104
|
+
|
|
105
|
+
Accepted values are:
|
|
106
|
+
|
|
107
|
+
NAME, TIMECREATED
|
|
108
|
+
|
|
109
|
+
--sort-order [text]
|
|
110
|
+
|
|
111
|
+
The sort order to use, either ascending (*ASC*) or descending
|
|
112
|
+
(*DESC*).
|
|
113
|
+
|
|
114
|
+
Accepted values are:
|
|
115
|
+
|
|
116
|
+
ASC, DESC
|
|
117
|
+
|
|
118
|
+
|
|
119
|
+
Global Parameters
|
|
120
|
+
=================
|
|
121
|
+
|
|
122
|
+
Use "oci --help" for help on global parameters.
|
|
123
|
+
|
|
124
|
+
"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
|
|
125
|
+
cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
|
|
126
|
+
defaults-file", "--endpoint", "--generate-full-command-json-input", "
|
|
127
|
+
--generate-param-json-input", "--help", "--latest-version", "--max-
|
|
128
|
+
retries", "--no-retry", "--opc-client-request-id", "--opc-request-id",
|
|
129
|
+
"--output", "--profile", "--proxy", "--query", "--raw-output", "--
|
|
130
|
+
read-timeout", "--realm-specific-endpoint", "--region", "--release-
|
|
131
|
+
info", "--request-id", "--version", "-?", "-d", "-h", "-i", "-v"
|
|
132
|
+
|
|
133
|
+
|
|
134
|
+
Example using required parameter
|
|
135
|
+
================================
|
|
136
|
+
|
|
137
|
+
Copy the following CLI commands into a file named example.sh. Run the
|
|
138
|
+
command by typing “bash example.sh” and replacing the example
|
|
139
|
+
parameters with your own.
|
|
140
|
+
|
|
141
|
+
Please note this sample will only work in the POSIX-compliant bash-
|
|
142
|
+
like shell. You need to set up the OCI configuration and appropriate
|
|
143
|
+
security policies before trying the examples.
|
|
144
|
+
|
|
145
|
+
oci db pluggable-database list-snapshots
|
|
@@ -28,16 +28,24 @@ Available Commands
|
|
|
28
28
|
|
|
29
29
|
* create-remote-clone
|
|
30
30
|
|
|
31
|
+
* create-snapshot
|
|
32
|
+
|
|
31
33
|
* delete
|
|
32
34
|
|
|
35
|
+
* delete-snapshot
|
|
36
|
+
|
|
33
37
|
* disable-pluggable-database-management
|
|
34
38
|
|
|
35
39
|
* enable-pluggable-database-management
|
|
36
40
|
|
|
37
41
|
* get
|
|
38
42
|
|
|
43
|
+
* get-snapshot
|
|
44
|
+
|
|
39
45
|
* list
|
|
40
46
|
|
|
47
|
+
* list-snapshots
|
|
48
|
+
|
|
41
49
|
* local-clone
|
|
42
50
|
|
|
43
51
|
* modify-pluggable-database-management
|
|
@@ -908,16 +908,24 @@ Available Commands
|
|
|
908
908
|
|
|
909
909
|
* create-remote-clone
|
|
910
910
|
|
|
911
|
+
* create-snapshot
|
|
912
|
+
|
|
911
913
|
* delete
|
|
912
914
|
|
|
915
|
+
* delete-snapshot
|
|
916
|
+
|
|
913
917
|
* disable-pluggable-database-management
|
|
914
918
|
|
|
915
919
|
* enable-pluggable-database-management
|
|
916
920
|
|
|
917
921
|
* get
|
|
918
922
|
|
|
923
|
+
* get-snapshot
|
|
924
|
+
|
|
919
925
|
* list
|
|
920
926
|
|
|
927
|
+
* list-snapshots
|
|
928
|
+
|
|
921
929
|
* local-clone
|
|
922
930
|
|
|
923
931
|
* modify-pluggable-database-management
|
|
@@ -1,5 +1,5 @@
|
|
|
1
|
-
"list"
|
|
2
|
-
|
|
1
|
+
"list-work-request-logs"
|
|
2
|
+
************************
|
|
3
3
|
|
|
4
4
|
* Description
|
|
5
5
|
|
|
@@ -24,7 +24,7 @@ ID.
|
|
|
24
24
|
Usage
|
|
25
25
|
=====
|
|
26
26
|
|
|
27
|
-
oci delegate-access-control work-request work-request-log list [OPTIONS]
|
|
27
|
+
oci delegate-access-control work-request work-request-log-entry list-work-request-logs [OPTIONS]
|
|
28
28
|
|
|
29
29
|
|
|
30
30
|
Required Parameters
|
|
@@ -123,6 +123,6 @@ Please note this sample will only work in the POSIX-compliant bash-
|
|
|
123
123
|
like shell. You need to set up the OCI configuration and appropriate
|
|
124
124
|
security policies before trying the examples.
|
|
125
125
|
|
|
126
|
-
export work_request_id=<substitute-value-of-work_request_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/delegate-access-control/work-request/work-request-log/list.html#cmdoption-work-request-id
|
|
126
|
+
export work_request_id=<substitute-value-of-work_request_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/delegate-access-control/work-request/work-request-log-entry/list-work-request-logs.html#cmdoption-work-request-id
|
|
127
127
|
|
|
128
|
-
oci delegate-access-control work-request work-request-log list --work-request-id $work_request_id
|
|
128
|
+
oci delegate-access-control work-request work-request-log-entry list-work-request-logs --work-request-id $work_request_id
|
|
@@ -1,5 +1,5 @@
|
|
|
1
|
-
work-request-log
|
|
2
|
-
|
|
1
|
+
work-request-log-entry
|
|
2
|
+
**********************
|
|
3
3
|
|
|
4
4
|
|
|
5
5
|
Description
|
|
@@ -11,4 +11,4 @@ A log message from the execution of a work request.
|
|
|
11
11
|
Available Commands
|
|
12
12
|
==================
|
|
13
13
|
|
|
14
|
-
* list
|
|
14
|
+
* list-work-request-logs
|