oci-cli 3.72.0__py3-none-any.whl → 3.72.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/bin/iot.psm1 +2 -2
- oci_cli/help_text_producer/data_files/text/cmdref/db/action-param-values-summary/list-params-for-action-type.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-container-database/create-autonomous-container-database-aws-encryption-key-details.txt +396 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-container-database/create-autonomous-container-database-azure-encryption-key-details.txt +396 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-container-database/create-autonomous-container-database-create-autonomous-container-database-details.txt +11 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-container-database/create-autonomous-container-database-create-autonomous-container-database-from-backup-details.txt +11 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-container-database/create-autonomous-container-database-external-hsm-encryption-details.txt +396 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-container-database/create-autonomous-container-database-google-cloud-provider-encryption-key-details.txt +396 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-container-database/create.txt +11 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-container-database.txt +9 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/change-disaster-recovery-configuration.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/configure-saas-admin-user.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/create-adb-cross-region-data-guard-details.txt +18 -2
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/create-autonomous-database-create-cross-region-disaster-recovery-details.txt +18 -2
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/create-autonomous-database-gcp-key-details.txt +18 -2
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/create-autonomous-database-undelete-autonomous-database-details.txt +18 -2
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/create-cross-tenancy-disaster-recovery-details.txt +18 -2
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/create-from-backup-id.txt +18 -2
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/create-from-backup-timestamp.txt +18 -2
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/create-from-clone.txt +18 -2
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/create-refreshable-clone.txt +18 -2
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/create.txt +18 -2
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/fail-over.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/import-transportable-tablespace.txt +142 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/list-clones.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/list.txt +2 -2
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/manual-refresh.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/restart.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/restore.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/rotate-key.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/shrink.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/start.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/stop.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/switchover.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/update-autonomous-database-gcp-key-details.txt +9 -4
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database/update.txt +9 -4
- oci_cli/help_text_producer/data_files/text/cmdref/db/autonomous-database.txt +2 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/cloud-autonomous-vm-cluster/register-cloud-autonomous-vm-cluster-pkcs.txt +140 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/cloud-autonomous-vm-cluster/unregister-cloud-autonomous-vm-cluster-pkcs.txt +140 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/cloud-autonomous-vm-cluster.txt +4 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/database/run-data-patch.txt +165 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/database/update.txt +11 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/database.txt +2 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/db-connection-bundle/download.txt +114 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/db-connection-bundle/get.txt +92 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/db-connection-bundle/list.txt +157 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/db-connection-bundle.txt +18 -0
- oci_cli/help_text_producer/data_files/text/cmdref/db/exascale-db-storage-vault/create.txt +3 -2
- oci_cli/help_text_producer/data_files/text/cmdref/db/exascale-db-storage-vault/update.txt +3 -2
- oci_cli/help_text_producer/data_files/text/cmdref/db/maintenance-run/create.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/db/maintenance-run/list.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/db/maintenance-run/update.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/db/maintenance-run-history/list.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/db/scheduled-action/create.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/db.txt +26 -0
- oci_cli/help_text_producer/data_files/text/cmdref/delegate-access-control/work-request/work-request-error/{list.txt → list-errors.txt} +5 -5
- oci_cli/help_text_producer/data_files/text/cmdref/delegate-access-control/work-request/work-request-error.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/delegate-access-control/work-request/{work-request-log-entry/list-work-request-logs.txt → work-request-log/list-logs.txt} +5 -5
- oci_cli/help_text_producer/data_files/text/cmdref/delegate-access-control/work-request/{work-request-log-entry.txt → work-request-log.txt} +3 -3
- oci_cli/help_text_producer/data_files/text/cmdref/delegate-access-control/work-request.txt +3 -3
- oci_cli/help_text_producer/data_files/text/cmdref/delegate-access-control.txt +3 -3
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai/api-key/change-compartment.txt +114 -0
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai/api-key/create.txt +181 -0
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai/api-key/delete.txt +138 -0
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai/api-key/get.txt +100 -0
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai/api-key/renew.txt +184 -0
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai/api-key/set-api-key-state.txt +181 -0
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai/api-key/update.txt +183 -0
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai/api-key-collection/list-api-keys.txt +150 -0
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai/api-key-collection.txt +14 -0
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai/api-key.txt +30 -0
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai/dedicated-ai-cluster/create.txt +6 -5
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai/endpoint/create.txt +22 -0
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai/endpoint/update.txt +22 -0
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai/generative-ai-private-endpoint/create.txt +5 -0
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai/generative-ai-private-endpoint/update.txt +5 -0
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai/model-collection/list-models.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai-inference/chat-result/chat-cohere-chat-request-v2.txt +350 -0
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai-inference/chat-result/chat-generic-chat-request.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai-inference/chat-result.txt +2 -0
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai-inference/embed-text-result/embed-text.txt +16 -0
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai-inference/rerank-text-result/rerank-text-dedicated-serving-mode.txt +4 -0
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai-inference/rerank-text-result/rerank-text-on-demand-serving-mode.txt +4 -0
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai-inference/rerank-text-result/rerank-text.txt +4 -0
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai-inference.txt +2 -0
- oci_cli/help_text_producer/data_files/text/cmdref/generative-ai.txt +20 -0
- oci_cli/help_text_producer/data_files/text/cmdref/iot/digital-twin-instance/get-content.txt +3 -2
- oci_cli/help_text_producer/data_files/text/cmdref/iot/domain-group/create.txt +10 -0
- oci_cli/help_text_producer/data_files/text/cmdref/iot/domain-group/list.txt +8 -0
- oci_cli/help_text_producer/data_files/text/cmdref/organizations/work-request-error/{list.txt → list-errors.txt} +5 -5
- oci_cli/help_text_producer/data_files/text/cmdref/organizations/work-request-error.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/organizations/{work-request-log-entry → work-request-log}/list.txt +19 -1
- oci_cli/help_text_producer/data_files/text/cmdref/organizations/{work-request-log-entry.txt → work-request-log.txt} +2 -2
- oci_cli/help_text_producer/data_files/text/cmdref/organizations.txt +2 -2
- oci_cli/version.py +1 -1
- {oci_cli-3.72.0.dist-info → oci_cli-3.72.1.dist-info}/METADATA +2 -2
- {oci_cli-3.72.0.dist-info → oci_cli-3.72.1.dist-info}/RECORD +107 -84
- services/database/src/oci_cli_database/generated/database_cli.py +1446 -140
- services/generative_ai/src/oci_cli_generative_ai/generated/generativeai_cli.py +519 -12
- services/generative_ai_inference/src/oci_cli_generative_ai_inference/generated/generativeaiinference_cli.py +169 -7
- services/identity/src/oci_cli_identity/identity_cli_extended.py +2 -0
- services/iot/src/oci_cli_iot/generated/iot_cli.py +10 -3
- {oci_cli-3.72.0.dist-info → oci_cli-3.72.1.dist-info}/LICENSE.txt +0 -0
- {oci_cli-3.72.0.dist-info → oci_cli-3.72.1.dist-info}/THIRD_PARTY_LICENSES.txt +0 -0
- {oci_cli-3.72.0.dist-info → oci_cli-3.72.1.dist-info}/WHEEL +0 -0
- {oci_cli-3.72.0.dist-info → oci_cli-3.72.1.dist-info}/entry_points.txt +0 -0
- {oci_cli-3.72.0.dist-info → oci_cli-3.72.1.dist-info}/top_level.txt +0 -0
|
@@ -0,0 +1,181 @@
|
|
|
1
|
+
"set-api-key-state"
|
|
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
|
+
Set state of the key.
|
|
21
|
+
|
|
22
|
+
|
|
23
|
+
Usage
|
|
24
|
+
=====
|
|
25
|
+
|
|
26
|
+
oci generative-ai api-key set-api-key-state [OPTIONS]
|
|
27
|
+
|
|
28
|
+
|
|
29
|
+
Required Parameters
|
|
30
|
+
===================
|
|
31
|
+
|
|
32
|
+
--api-key-id [text]
|
|
33
|
+
|
|
34
|
+
The OCID of the APIKey.
|
|
35
|
+
|
|
36
|
+
--key-name [text]
|
|
37
|
+
|
|
38
|
+
The key to set state.
|
|
39
|
+
|
|
40
|
+
--state [text]
|
|
41
|
+
|
|
42
|
+
The target state of the API key item.
|
|
43
|
+
|
|
44
|
+
|
|
45
|
+
Optional Parameters
|
|
46
|
+
===================
|
|
47
|
+
|
|
48
|
+
--defined-tags [complex type]
|
|
49
|
+
|
|
50
|
+
Defined tags for this resource. Each key is predefined and scoped to a
|
|
51
|
+
namespace. For more information, see Resource Tags.
|
|
52
|
+
|
|
53
|
+
Example:
|
|
54
|
+
|
|
55
|
+
{"Operations": {"CostCenter": "42"}}
|
|
56
|
+
|
|
57
|
+
This is a complex type whose value must be valid JSON. The value can
|
|
58
|
+
be provided as a string on the command line or passed in as a file
|
|
59
|
+
using the file://path/to/file syntax.
|
|
60
|
+
|
|
61
|
+
The "--generate-param-json-input" option can be used to generate an
|
|
62
|
+
example of the JSON which must be provided. We recommend storing this
|
|
63
|
+
example in a file, modifying it as needed and then passing it back in
|
|
64
|
+
via the file:// syntax.
|
|
65
|
+
|
|
66
|
+
--freeform-tags [complex type]
|
|
67
|
+
|
|
68
|
+
Free-form tags for this resource. Each tag is a simple key-value pair
|
|
69
|
+
with no predefined name, type, or namespace. For more information, see
|
|
70
|
+
Resource Tags.
|
|
71
|
+
|
|
72
|
+
Example:
|
|
73
|
+
|
|
74
|
+
{"Department": "Finance"}
|
|
75
|
+
|
|
76
|
+
This is a complex type whose value must be valid JSON. The value can
|
|
77
|
+
be provided as a string on the command line or passed in as a file
|
|
78
|
+
using the file://path/to/file syntax.
|
|
79
|
+
|
|
80
|
+
The "--generate-param-json-input" option can be used to generate an
|
|
81
|
+
example of the JSON which must be provided. We recommend storing this
|
|
82
|
+
example in a file, modifying it as needed and then passing it back in
|
|
83
|
+
via the file:// syntax.
|
|
84
|
+
|
|
85
|
+
--from-json [text]
|
|
86
|
+
|
|
87
|
+
Provide input to this command as a JSON document from a file using the
|
|
88
|
+
file://path-to/file syntax.
|
|
89
|
+
|
|
90
|
+
The "--generate-full-command-json-input" option can be used to
|
|
91
|
+
generate a sample json file to be used with this command option. The
|
|
92
|
+
key names are pre-populated and match the command option names
|
|
93
|
+
(converted to camelCase format, e.g. compartment-id –> compartmentId),
|
|
94
|
+
while the values of the keys need to be populated by the user before
|
|
95
|
+
using the sample file as an input to this command. For any command
|
|
96
|
+
option that accepts multiple values, the value of the key can be a
|
|
97
|
+
JSON array.
|
|
98
|
+
|
|
99
|
+
Options can still be provided on the command line. If an option exists
|
|
100
|
+
in both the JSON document and the command line then the command line
|
|
101
|
+
specified value will be used.
|
|
102
|
+
|
|
103
|
+
For examples on usage of this option, please see our “using CLI with
|
|
104
|
+
advanced JSON options” link: https://docs.cloud.oracle.com/iaas/Conte
|
|
105
|
+
nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
|
|
106
|
+
|
|
107
|
+
--if-match [text]
|
|
108
|
+
|
|
109
|
+
For optimistic concurrency control. In the PUT or DELETE call for a
|
|
110
|
+
resource, set the *if-match* parameter to the value of the etag from a
|
|
111
|
+
previous GET or POST response for that resource. The resource will be
|
|
112
|
+
updated or deleted only if the etag you provide matches the resource’s
|
|
113
|
+
current etag value.
|
|
114
|
+
|
|
115
|
+
--max-wait-seconds [integer]
|
|
116
|
+
|
|
117
|
+
The maximum time to wait for the resource to reach the lifecycle state
|
|
118
|
+
defined by "--wait-for-state". Defaults to 1200 seconds.
|
|
119
|
+
|
|
120
|
+
--wait-for-state [text]
|
|
121
|
+
|
|
122
|
+
This operation creates, modifies or deletes a resource that has a
|
|
123
|
+
defined lifecycle state. Specify this option to perform the action and
|
|
124
|
+
then wait until the resource reaches a given lifecycle state. Multiple
|
|
125
|
+
states can be specified, returning on the first state. For example, "
|
|
126
|
+
--wait-for-state" SUCCEEDED "--wait-for-state" FAILED would return on
|
|
127
|
+
whichever lifecycle state is reached first. If timeout is reached, a
|
|
128
|
+
return code of 2 is returned. For any other error, a return code of 1
|
|
129
|
+
is returned.
|
|
130
|
+
|
|
131
|
+
Accepted values are:
|
|
132
|
+
|
|
133
|
+
ACTIVE, CREATING, DELETED, DELETING, FAILED, UPDATING
|
|
134
|
+
|
|
135
|
+
--wait-interval-seconds [integer]
|
|
136
|
+
|
|
137
|
+
Check every "--wait-interval-seconds" to see whether the resource has
|
|
138
|
+
reached the lifecycle state defined by "--wait-for-state". Defaults to
|
|
139
|
+
30 seconds.
|
|
140
|
+
|
|
141
|
+
|
|
142
|
+
Global Parameters
|
|
143
|
+
=================
|
|
144
|
+
|
|
145
|
+
Use "oci --help" for help on global parameters.
|
|
146
|
+
|
|
147
|
+
"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
|
|
148
|
+
cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
|
|
149
|
+
defaults-file", "--enable-dual-stack", "--enable-propagation", "--
|
|
150
|
+
endpoint", "--generate-full-command-json-input", "--generate-param-
|
|
151
|
+
json-input", "--help", "--latest-version", "--max-retries", "--no-
|
|
152
|
+
retry", "--opc-client-request-id", "--opc-request-id", "--output", "--
|
|
153
|
+
profile", "--proxy", "--query", "--raw-output", "--read-timeout", "--
|
|
154
|
+
realm-specific-endpoint", "--region", "--release-info", "--request-
|
|
155
|
+
id", "--version", "-?", "-d", "-h", "-i", "-v"
|
|
156
|
+
|
|
157
|
+
|
|
158
|
+
Example using required parameter
|
|
159
|
+
================================
|
|
160
|
+
|
|
161
|
+
Copy and paste the following example into a JSON file, replacing the
|
|
162
|
+
example parameters with your own.
|
|
163
|
+
|
|
164
|
+
oci generative-ai api-key create --generate-param-json-input key-details > key-details.json
|
|
165
|
+
|
|
166
|
+
Copy the following CLI commands into a file named example.sh. Run the
|
|
167
|
+
command by typing “bash example.sh” and replacing the example
|
|
168
|
+
parameters with your own.
|
|
169
|
+
|
|
170
|
+
Please note this sample will only work in the POSIX-compliant bash-
|
|
171
|
+
like shell. You need to set up the OCI configuration and appropriate
|
|
172
|
+
security policies before trying the examples.
|
|
173
|
+
|
|
174
|
+
export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/generative-ai/api-key/create.html#cmdoption-compartment-id
|
|
175
|
+
export display_name=<substitute-value-of-display_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/generative-ai/api-key/create.html#cmdoption-display-name
|
|
176
|
+
export key_name=<substitute-value-of-key_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/generative-ai/api-key/set-api-key-state.html#cmdoption-key-name
|
|
177
|
+
export state=<substitute-value-of-state> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/generative-ai/api-key/set-api-key-state.html#cmdoption-state
|
|
178
|
+
|
|
179
|
+
api_key_id=$(oci generative-ai api-key create --compartment-id $compartment_id --display-name $display_name --key-details file://key-details.json --query data.id --raw-output)
|
|
180
|
+
|
|
181
|
+
oci generative-ai api-key set-api-key-state --api-key-id $api_key_id --key-name $key_name --state $state
|
|
@@ -0,0 +1,183 @@
|
|
|
1
|
+
"update"
|
|
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
|
+
Updates the properties of an apiKey.
|
|
21
|
+
|
|
22
|
+
|
|
23
|
+
Usage
|
|
24
|
+
=====
|
|
25
|
+
|
|
26
|
+
oci generative-ai api-key update [OPTIONS]
|
|
27
|
+
|
|
28
|
+
|
|
29
|
+
Required Parameters
|
|
30
|
+
===================
|
|
31
|
+
|
|
32
|
+
--api-key-id [text]
|
|
33
|
+
|
|
34
|
+
The OCID of the APIKey.
|
|
35
|
+
|
|
36
|
+
|
|
37
|
+
Optional Parameters
|
|
38
|
+
===================
|
|
39
|
+
|
|
40
|
+
--defined-tags [complex type]
|
|
41
|
+
|
|
42
|
+
Defined tags for this resource. Each key is predefined and scoped to a
|
|
43
|
+
namespace. For more information, see Resource Tags.
|
|
44
|
+
|
|
45
|
+
Example:
|
|
46
|
+
|
|
47
|
+
{"Operations": {"CostCenter": "42"}}
|
|
48
|
+
|
|
49
|
+
This is a complex type whose value must be valid JSON. The value can
|
|
50
|
+
be provided as a string on the command line or passed in as a file
|
|
51
|
+
using the 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
|
+
--description [text]
|
|
59
|
+
|
|
60
|
+
An optional description of the Api key.
|
|
61
|
+
|
|
62
|
+
--display-name [text]
|
|
63
|
+
|
|
64
|
+
A user-friendly name. Does not have to be unique, and it’s changeable.
|
|
65
|
+
|
|
66
|
+
--force
|
|
67
|
+
|
|
68
|
+
Perform update without prompting for confirmation.
|
|
69
|
+
|
|
70
|
+
--freeform-tags [complex type]
|
|
71
|
+
|
|
72
|
+
Free-form tags for this resource. Each tag is a simple key-value pair
|
|
73
|
+
with no predefined name, type, or namespace. For more information, see
|
|
74
|
+
Resource Tags.
|
|
75
|
+
|
|
76
|
+
Example:
|
|
77
|
+
|
|
78
|
+
{"Department": "Finance"}
|
|
79
|
+
|
|
80
|
+
This is a complex type whose value must be valid JSON. The value can
|
|
81
|
+
be provided as a string on the command line or passed in as a file
|
|
82
|
+
using the file://path/to/file syntax.
|
|
83
|
+
|
|
84
|
+
The "--generate-param-json-input" option can be used to generate an
|
|
85
|
+
example of the JSON which must be provided. We recommend storing this
|
|
86
|
+
example in a file, modifying it as needed and then passing it back in
|
|
87
|
+
via the file:// syntax.
|
|
88
|
+
|
|
89
|
+
--from-json [text]
|
|
90
|
+
|
|
91
|
+
Provide input to this command as a JSON document from a file using the
|
|
92
|
+
file://path-to/file syntax.
|
|
93
|
+
|
|
94
|
+
The "--generate-full-command-json-input" option can be used to
|
|
95
|
+
generate a sample json file to be used with this command option. The
|
|
96
|
+
key names are pre-populated and match the command option names
|
|
97
|
+
(converted to camelCase format, e.g. compartment-id –> compartmentId),
|
|
98
|
+
while the values of the keys need to be populated by the user before
|
|
99
|
+
using the sample file as an input to this command. For any command
|
|
100
|
+
option that accepts multiple values, the value of the key can be a
|
|
101
|
+
JSON array.
|
|
102
|
+
|
|
103
|
+
Options can still be provided on the command line. If an option exists
|
|
104
|
+
in both the JSON document and the command line then the command line
|
|
105
|
+
specified value will be used.
|
|
106
|
+
|
|
107
|
+
For examples on usage of this option, please see our “using CLI with
|
|
108
|
+
advanced JSON options” link: https://docs.cloud.oracle.com/iaas/Conte
|
|
109
|
+
nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
|
|
110
|
+
|
|
111
|
+
--if-match [text]
|
|
112
|
+
|
|
113
|
+
For optimistic concurrency control. In the PUT or DELETE call for a
|
|
114
|
+
resource, set the *if-match* parameter to the value of the etag from a
|
|
115
|
+
previous GET or POST response for that resource. The resource will be
|
|
116
|
+
updated or deleted only if the etag you provide matches the resource’s
|
|
117
|
+
current etag value.
|
|
118
|
+
|
|
119
|
+
--max-wait-seconds [integer]
|
|
120
|
+
|
|
121
|
+
The maximum time to wait for the resource to reach the lifecycle state
|
|
122
|
+
defined by "--wait-for-state". Defaults to 1200 seconds.
|
|
123
|
+
|
|
124
|
+
--wait-for-state [text]
|
|
125
|
+
|
|
126
|
+
This operation creates, modifies or deletes a resource that has a
|
|
127
|
+
defined lifecycle state. Specify this option to perform the action and
|
|
128
|
+
then wait until the resource reaches a given lifecycle state. Multiple
|
|
129
|
+
states can be specified, returning on the first state. For example, "
|
|
130
|
+
--wait-for-state" SUCCEEDED "--wait-for-state" FAILED would return on
|
|
131
|
+
whichever lifecycle state is reached first. If timeout is reached, a
|
|
132
|
+
return code of 2 is returned. For any other error, a return code of 1
|
|
133
|
+
is returned.
|
|
134
|
+
|
|
135
|
+
Accepted values are:
|
|
136
|
+
|
|
137
|
+
ACTIVE, CREATING, DELETED, DELETING, FAILED, UPDATING
|
|
138
|
+
|
|
139
|
+
--wait-interval-seconds [integer]
|
|
140
|
+
|
|
141
|
+
Check every "--wait-interval-seconds" to see whether the resource has
|
|
142
|
+
reached the lifecycle state defined by "--wait-for-state". Defaults to
|
|
143
|
+
30 seconds.
|
|
144
|
+
|
|
145
|
+
|
|
146
|
+
Global Parameters
|
|
147
|
+
=================
|
|
148
|
+
|
|
149
|
+
Use "oci --help" for help on global parameters.
|
|
150
|
+
|
|
151
|
+
"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
|
|
152
|
+
cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
|
|
153
|
+
defaults-file", "--enable-dual-stack", "--enable-propagation", "--
|
|
154
|
+
endpoint", "--generate-full-command-json-input", "--generate-param-
|
|
155
|
+
json-input", "--help", "--latest-version", "--max-retries", "--no-
|
|
156
|
+
retry", "--opc-client-request-id", "--opc-request-id", "--output", "--
|
|
157
|
+
profile", "--proxy", "--query", "--raw-output", "--read-timeout", "--
|
|
158
|
+
realm-specific-endpoint", "--region", "--release-info", "--request-
|
|
159
|
+
id", "--version", "-?", "-d", "-h", "-i", "-v"
|
|
160
|
+
|
|
161
|
+
|
|
162
|
+
Example using required parameter
|
|
163
|
+
================================
|
|
164
|
+
|
|
165
|
+
Copy and paste the following example into a JSON file, replacing the
|
|
166
|
+
example parameters with your own.
|
|
167
|
+
|
|
168
|
+
oci generative-ai api-key create --generate-param-json-input key-details > key-details.json
|
|
169
|
+
|
|
170
|
+
Copy the following CLI commands into a file named example.sh. Run the
|
|
171
|
+
command by typing “bash example.sh” and replacing the example
|
|
172
|
+
parameters with your own.
|
|
173
|
+
|
|
174
|
+
Please note this sample will only work in the POSIX-compliant bash-
|
|
175
|
+
like shell. You need to set up the OCI configuration and appropriate
|
|
176
|
+
security policies before trying the examples.
|
|
177
|
+
|
|
178
|
+
export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/generative-ai/api-key/create.html#cmdoption-compartment-id
|
|
179
|
+
export display_name=<substitute-value-of-display_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/generative-ai/api-key/create.html#cmdoption-display-name
|
|
180
|
+
|
|
181
|
+
api_key_id=$(oci generative-ai api-key create --compartment-id $compartment_id --display-name $display_name --key-details file://key-details.json --query data.id --raw-output)
|
|
182
|
+
|
|
183
|
+
oci generative-ai api-key update --api-key-id $api_key_id
|
oci_cli/help_text_producer/data_files/text/cmdref/generative-ai/api-key-collection/list-api-keys.txt
ADDED
|
@@ -0,0 +1,150 @@
|
|
|
1
|
+
"list-api-keys"
|
|
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
|
+
Lists the ApiKeys of a specific compartment.
|
|
21
|
+
|
|
22
|
+
|
|
23
|
+
Usage
|
|
24
|
+
=====
|
|
25
|
+
|
|
26
|
+
oci generative-ai api-key-collection list-api-keys [OPTIONS]
|
|
27
|
+
|
|
28
|
+
|
|
29
|
+
Required Parameters
|
|
30
|
+
===================
|
|
31
|
+
|
|
32
|
+
--compartment-id, -c [text]
|
|
33
|
+
|
|
34
|
+
The OCID of the compartment in which to list resources.
|
|
35
|
+
|
|
36
|
+
|
|
37
|
+
Optional Parameters
|
|
38
|
+
===================
|
|
39
|
+
|
|
40
|
+
--all
|
|
41
|
+
|
|
42
|
+
Fetches all pages of results. If you provide this option, then you
|
|
43
|
+
cannot provide the "--limit" option.
|
|
44
|
+
|
|
45
|
+
--display-name [text]
|
|
46
|
+
|
|
47
|
+
A filter to return only resources that match the given display name
|
|
48
|
+
exactly.
|
|
49
|
+
|
|
50
|
+
--from-json [text]
|
|
51
|
+
|
|
52
|
+
Provide input to this command as a JSON document from a file using the
|
|
53
|
+
file://path-to/file syntax.
|
|
54
|
+
|
|
55
|
+
The "--generate-full-command-json-input" option can be used to
|
|
56
|
+
generate a sample json file to be used with this command option. The
|
|
57
|
+
key names are pre-populated and match the command option names
|
|
58
|
+
(converted to camelCase format, e.g. compartment-id –> compartmentId),
|
|
59
|
+
while the values of the keys need to be populated by the user before
|
|
60
|
+
using the sample file as an input to this command. For any command
|
|
61
|
+
option that accepts multiple values, the value of the key can be a
|
|
62
|
+
JSON array.
|
|
63
|
+
|
|
64
|
+
Options can still be provided on the command line. If an option exists
|
|
65
|
+
in both the JSON document and the command line then the command line
|
|
66
|
+
specified value will be used.
|
|
67
|
+
|
|
68
|
+
For examples on usage of this option, please see our “using CLI with
|
|
69
|
+
advanced JSON options” link: https://docs.cloud.oracle.com/iaas/Conte
|
|
70
|
+
nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
|
|
71
|
+
|
|
72
|
+
--id [text]
|
|
73
|
+
|
|
74
|
+
The OCID of the APIKey.
|
|
75
|
+
|
|
76
|
+
--lifecycle-state [text]
|
|
77
|
+
|
|
78
|
+
A filter to return only resources that their lifecycle state matches
|
|
79
|
+
the given lifecycle state.
|
|
80
|
+
|
|
81
|
+
Accepted values are:
|
|
82
|
+
|
|
83
|
+
ACTIVE, CREATING, DELETED, DELETING, FAILED, UPDATING
|
|
84
|
+
|
|
85
|
+
--limit [integer]
|
|
86
|
+
|
|
87
|
+
For list pagination. The maximum number of results per page, or items
|
|
88
|
+
to return in a paginated “List” call. For important details about how
|
|
89
|
+
pagination works, see List Pagination.
|
|
90
|
+
|
|
91
|
+
--page [text]
|
|
92
|
+
|
|
93
|
+
For list pagination. The value of the opc-next-page response header
|
|
94
|
+
from the previous “List” call. For important details about how
|
|
95
|
+
pagination works, see List Pagination.
|
|
96
|
+
|
|
97
|
+
--page-size [integer]
|
|
98
|
+
|
|
99
|
+
When fetching results, the number of results to fetch per call. Only
|
|
100
|
+
valid when used with "--all" or "--limit", and ignored otherwise.
|
|
101
|
+
|
|
102
|
+
--sort-by [text]
|
|
103
|
+
|
|
104
|
+
The field to sort by. You can provide only one sort order. Default
|
|
105
|
+
order for *timeCreated* is descending. Default order for *displayName*
|
|
106
|
+
is ascending.
|
|
107
|
+
|
|
108
|
+
Accepted values are:
|
|
109
|
+
|
|
110
|
+
displayName, timeCreated
|
|
111
|
+
|
|
112
|
+
--sort-order [text]
|
|
113
|
+
|
|
114
|
+
The sort order to use, either ‘ASC’ or ‘DESC’.
|
|
115
|
+
|
|
116
|
+
Accepted values are:
|
|
117
|
+
|
|
118
|
+
ASC, DESC
|
|
119
|
+
|
|
120
|
+
|
|
121
|
+
Global Parameters
|
|
122
|
+
=================
|
|
123
|
+
|
|
124
|
+
Use "oci --help" for help on global parameters.
|
|
125
|
+
|
|
126
|
+
"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
|
|
127
|
+
cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
|
|
128
|
+
defaults-file", "--enable-dual-stack", "--enable-propagation", "--
|
|
129
|
+
endpoint", "--generate-full-command-json-input", "--generate-param-
|
|
130
|
+
json-input", "--help", "--latest-version", "--max-retries", "--no-
|
|
131
|
+
retry", "--opc-client-request-id", "--opc-request-id", "--output", "--
|
|
132
|
+
profile", "--proxy", "--query", "--raw-output", "--read-timeout", "--
|
|
133
|
+
realm-specific-endpoint", "--region", "--release-info", "--request-
|
|
134
|
+
id", "--version", "-?", "-d", "-h", "-i", "-v"
|
|
135
|
+
|
|
136
|
+
|
|
137
|
+
Example using required parameter
|
|
138
|
+
================================
|
|
139
|
+
|
|
140
|
+
Copy the following CLI commands into a file named example.sh. Run the
|
|
141
|
+
command by typing “bash example.sh” and replacing the example
|
|
142
|
+
parameters with your own.
|
|
143
|
+
|
|
144
|
+
Please note this sample will only work in the POSIX-compliant bash-
|
|
145
|
+
like shell. You need to set up the OCI configuration and appropriate
|
|
146
|
+
security policies before trying the examples.
|
|
147
|
+
|
|
148
|
+
export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/generative-ai/api-key-collection/list-api-keys.html#cmdoption-compartment-id
|
|
149
|
+
|
|
150
|
+
oci generative-ai api-key-collection list-api-keys --compartment-id $compartment_id
|
|
@@ -0,0 +1,30 @@
|
|
|
1
|
+
api-key
|
|
2
|
+
*******
|
|
3
|
+
|
|
4
|
+
|
|
5
|
+
Description
|
|
6
|
+
===========
|
|
7
|
+
|
|
8
|
+
ApiKeys are resources used to access GenAI models. You must be
|
|
9
|
+
authorized through an IAM policy to use any API operations. If you’re
|
|
10
|
+
not authorized, contact an administrator who manages OCI resource
|
|
11
|
+
access. See Getting Started with Policies and Getting Access to
|
|
12
|
+
Generative AI Resources.
|
|
13
|
+
|
|
14
|
+
|
|
15
|
+
Available Commands
|
|
16
|
+
==================
|
|
17
|
+
|
|
18
|
+
* change-compartment
|
|
19
|
+
|
|
20
|
+
* create
|
|
21
|
+
|
|
22
|
+
* delete
|
|
23
|
+
|
|
24
|
+
* get
|
|
25
|
+
|
|
26
|
+
* renew
|
|
27
|
+
|
|
28
|
+
* set-api-key-state
|
|
29
|
+
|
|
30
|
+
* update
|
oci_cli/help_text_producer/data_files/text/cmdref/generative-ai/dedicated-ai-cluster/create.txt
CHANGED
|
@@ -52,11 +52,12 @@ hardware configuration is hidden from customers.
|
|
|
52
52
|
Allowed values are: - LARGE_COHERE - LARGE_COHERE_V2 - SMALL_COHERE -
|
|
53
53
|
SMALL_COHERE_V2 - SMALL_COHERE_4 - EMBED_COHERE - LLAMA2_70 -
|
|
54
54
|
LARGE_GENERIC - LARGE_COHERE_V2_2 - LARGE_GENERIC_4 - SMALL_GENERIC_V2
|
|
55
|
-
- LARGE_GENERIC_2 -
|
|
56
|
-
- MEDIUM_GENERIC_V1 - LARGE_GENERIC_V1 - A10_X1 -
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
- H100_X8 - H200_X1 - H200_X2 - H200_X4 -
|
|
55
|
+
- LARGE_GENERIC_2 - LARGE_GENERIC_V3 - LARGE_COHERE_V3 - RERANK_COHERE
|
|
56
|
+
- SMALL_GENERIC_V1 - MEDIUM_GENERIC_V1 - LARGE_GENERIC_V1 - A10_X1 -
|
|
57
|
+
A10_X2 - A10_X4 - A100_40G_X1 - A100_40G_X2 - A100_40G_X4 -
|
|
58
|
+
A100_40G_X8 - A100_80G_X1 - A100_80G_X2 - A100_80G_X4 - A100_80G_X8 -
|
|
59
|
+
H100_X1 - H100_X2 - H100_X4 - H100_X8 - H200_X1 - H200_X2 - H200_X4 -
|
|
60
|
+
H200_X8
|
|
60
61
|
|
|
61
62
|
The following shapes can only be used to deploy imported models: -
|
|
62
63
|
A10_X1, A10_X2, A10_X4 - A100_40G_X1, A100_40G_X2, A100_40G_X4,
|
|
@@ -137,6 +137,28 @@ is attached to.
|
|
|
137
137
|
The maximum time to wait for the work request to reach the state
|
|
138
138
|
defined by "--wait-for-state". Defaults to 1200 seconds.
|
|
139
139
|
|
|
140
|
+
--pii-detection-config [complex type]
|
|
141
|
+
|
|
142
|
+
This is a complex type whose value must be valid JSON. The value can
|
|
143
|
+
be provided as a string on the command line or passed in as a file
|
|
144
|
+
using the file://path/to/file syntax.
|
|
145
|
+
|
|
146
|
+
The "--generate-param-json-input" option can be used to generate an
|
|
147
|
+
example of the JSON which must be provided. We recommend storing this
|
|
148
|
+
example in a file, modifying it as needed and then passing it back in
|
|
149
|
+
via the file:// syntax.
|
|
150
|
+
|
|
151
|
+
--prompt-injection-config [complex type]
|
|
152
|
+
|
|
153
|
+
This is a complex type whose value must be valid JSON. The value can
|
|
154
|
+
be provided as a string on the command line or passed in as a file
|
|
155
|
+
using the file://path/to/file syntax.
|
|
156
|
+
|
|
157
|
+
The "--generate-param-json-input" option can be used to generate an
|
|
158
|
+
example of the JSON which must be provided. We recommend storing this
|
|
159
|
+
example in a file, modifying it as needed and then passing it back in
|
|
160
|
+
via the file:// syntax.
|
|
161
|
+
|
|
140
162
|
--wait-for-state [text]
|
|
141
163
|
|
|
142
164
|
This operation asynchronously creates, modifies or deletes a resource
|
|
@@ -137,6 +137,28 @@ current etag value.
|
|
|
137
137
|
The maximum time to wait for the work request to reach the state
|
|
138
138
|
defined by "--wait-for-state". Defaults to 1200 seconds.
|
|
139
139
|
|
|
140
|
+
--pii-detection-config [complex type]
|
|
141
|
+
|
|
142
|
+
This is a complex type whose value must be valid JSON. The value can
|
|
143
|
+
be provided as a string on the command line or passed in as a file
|
|
144
|
+
using the file://path/to/file syntax.
|
|
145
|
+
|
|
146
|
+
The "--generate-param-json-input" option can be used to generate an
|
|
147
|
+
example of the JSON which must be provided. We recommend storing this
|
|
148
|
+
example in a file, modifying it as needed and then passing it back in
|
|
149
|
+
via the file:// syntax.
|
|
150
|
+
|
|
151
|
+
--prompt-injection-config [complex type]
|
|
152
|
+
|
|
153
|
+
This is a complex type whose value must be valid JSON. The value can
|
|
154
|
+
be provided as a string on the command line or passed in as a file
|
|
155
|
+
using the file://path/to/file syntax.
|
|
156
|
+
|
|
157
|
+
The "--generate-param-json-input" option can be used to generate an
|
|
158
|
+
example of the JSON which must be provided. We recommend storing this
|
|
159
|
+
example in a file, modifying it as needed and then passing it back in
|
|
160
|
+
via the file:// syntax.
|
|
161
|
+
|
|
140
162
|
--wait-for-state [text]
|
|
141
163
|
|
|
142
164
|
This operation asynchronously creates, modifies or deletes a resource
|
|
@@ -114,6 +114,11 @@ For examples on usage of this option, please see our “using CLI with
|
|
|
114
114
|
advanced JSON options” link: https://docs.cloud.oracle.com/iaas/Conte
|
|
115
115
|
nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
|
|
116
116
|
|
|
117
|
+
--is-allow-on-demand [boolean]
|
|
118
|
+
|
|
119
|
+
Flag that allows access to on-demand models using this private
|
|
120
|
+
endpoint.
|
|
121
|
+
|
|
117
122
|
--max-wait-seconds [integer]
|
|
118
123
|
|
|
119
124
|
The maximum time to wait for the work request to reach the state
|
|
@@ -121,6 +121,11 @@ previous GET or POST response for that resource. The resource will be
|
|
|
121
121
|
updated or deleted only if the etag you provide matches the resource’s
|
|
122
122
|
current etag value.
|
|
123
123
|
|
|
124
|
+
--is-allow-on-demand [boolean]
|
|
125
|
+
|
|
126
|
+
Flag that allows access to on-demand models using this private
|
|
127
|
+
endpoint.
|
|
128
|
+
|
|
124
129
|
--max-wait-seconds [integer]
|
|
125
130
|
|
|
126
131
|
The maximum time to wait for the work request to reach the state
|