oci-cli 3.68.0__py3-none-any.whl → 3.68.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/devops.psm1 +12 -1
- oci_cli/bin/streaming.psm1 +2 -2
- oci_cli/help_text_producer/data_files/text/cmdref/data-science/job-run/create.txt +17 -0
- oci_cli/help_text_producer/data_files/text/cmdref/data-science/pipeline/create.txt +12 -0
- oci_cli/help_text_producer/data_files/text/cmdref/data-science/pipeline/update.txt +12 -0
- oci_cli/help_text_producer/data_files/text/cmdref/data-science/pipeline-run/create.txt +30 -0
- oci_cli/help_text_producer/data_files/text/cmdref/devops/trigger-dry-run-result/trigger-deployment-dry-run-create-deploy-pipeline-deployment-details.txt +174 -0
- oci_cli/help_text_producer/data_files/text/cmdref/devops/trigger-dry-run-result/trigger-deployment-dry-run-create-deploy-pipeline-redeployment-details.txt +146 -0
- oci_cli/help_text_producer/data_files/text/cmdref/devops/trigger-dry-run-result/trigger-deployment-dry-run-create-single-deploy-stage-deployment-details.txt +179 -0
- oci_cli/help_text_producer/data_files/text/cmdref/devops/trigger-dry-run-result/trigger-deployment-dry-run-create-single-deploy-stage-redeployment-details.txt +150 -0
- oci_cli/help_text_producer/data_files/text/cmdref/devops/trigger-dry-run-result/trigger-deployment-dry-run.txt +116 -0
- oci_cli/help_text_producer/data_files/text/cmdref/devops/trigger-dry-run-result.txt +25 -0
- oci_cli/help_text_producer/data_files/text/cmdref/devops.txt +16 -0
- oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-collection/create-db.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-collection/create-gi.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-discovery/create-db.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-discovery/create-gi.txt +1 -1
- oci_cli/help_text_producer/data_files/text/cmdref/governance-rules-control-plane/work-request/work-request-error/{list-errors.txt → list.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/{list-logs.txt → list.txt} +5 -5
- oci_cli/help_text_producer/data_files/text/cmdref/governance-rules-control-plane/work-request/work-request-log.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/session/authenticate.txt +4 -4
- oci_cli/help_text_producer/data_files/text/cmdref/streaming/admin/stream-pool/create.txt +18 -0
- oci_cli/help_text_producer/data_files/text/cmdref/streaming/admin/stream-pool/update.txt +18 -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.68.0.dist-info → oci_cli-3.68.1.dist-info}/METADATA +7 -3
- {oci_cli-3.68.0.dist-info → oci_cli-3.68.1.dist-info}/RECORD +45 -39
- services/data_science/src/oci_cli_data_science/generated/datascience_cli.py +139 -49
- services/devops/src/oci_cli_devops/generated/devops_cli.py +226 -0
- services/fleet_software_update/src/oci_cli_fleet_software_update/generated/fleetsoftwareupdate_cli.py +4 -4
- services/golden_gate/src/oci_cli_golden_gate/generated/goldengate_cli.py +6 -6
- services/streaming/src/oci_cli_stream_admin/generated/streamadmin_cli.py +20 -8
- {oci_cli-3.68.0.dist-info → oci_cli-3.68.1.dist-info}/LICENSE.txt +0 -0
- {oci_cli-3.68.0.dist-info → oci_cli-3.68.1.dist-info}/THIRD_PARTY_LICENSES.txt +0 -0
- {oci_cli-3.68.0.dist-info → oci_cli-3.68.1.dist-info}/WHEEL +0 -0
- {oci_cli-3.68.0.dist-info → oci_cli-3.68.1.dist-info}/entry_points.txt +0 -0
- {oci_cli-3.68.0.dist-info → oci_cli-3.68.1.dist-info}/top_level.txt +0 -0
oci_cli/bin/devops.psm1
CHANGED
|
@@ -4,7 +4,7 @@ function GetOciTopLevelCommand_devops() {
|
|
|
4
4
|
|
|
5
5
|
function GetOciSubcommands_devops() {
|
|
6
6
|
$ociSubcommands = @{
|
|
7
|
-
'devops' = 'build-pipeline build-pipeline-stage build-run connection deploy-artifact deploy-environment deploy-pipeline deploy-stage deployment project protected-branch protected-branch-collection pull-request pull-request-comment repository repository-path-summary trigger work-request work-request-error work-request-log'
|
|
7
|
+
'devops' = 'build-pipeline build-pipeline-stage build-run connection deploy-artifact deploy-environment deploy-pipeline deploy-stage deployment project protected-branch protected-branch-collection pull-request pull-request-comment repository repository-path-summary trigger trigger-dry-run-result work-request work-request-error work-request-log'
|
|
8
8
|
'devops build-pipeline' = 'create delete get list update'
|
|
9
9
|
'devops build-pipeline-stage' = 'create-build-stage create-deliver-artifact-stage create-trigger-deployment-stage create-wait-stage delete get list update-build-stage update-deliver-artifact-stage update-trigger-deployment-stage update-wait-stage'
|
|
10
10
|
'devops build-run' = 'cancel create get list update'
|
|
@@ -22,6 +22,7 @@ function GetOciSubcommands_devops() {
|
|
|
22
22
|
'devops repository' = 'create create-or-update-git-branch-details create-or-update-git-tag-details delete delete-git-ref delete-ref delete-repository-settings get get-commit get-commit-diff get-file-diff get-mirror-record get-object get-object-content get-ref get-repo-file-diff get-repo-file-lines get-repository-archive-content get-repository-file-lines get-repository-notification-preference get-repository-settings list list-authors list-commit-diffs list-commits list-fork-sync-statuses list-mirror-records list-pull-request-authors list-refs list-repository-analytics-authors mirror put-repository-ref-branch-details put-repository-ref-tag-details summarize-repository-analytics sync update update-repository-notification-preference update-repository-settings'
|
|
23
23
|
'devops repository-path-summary' = 'list-paths'
|
|
24
24
|
'devops trigger' = 'create-bitbucket-cloud-trigger create-bitbucket-server-trigger create-devops-code-repo-trigger create-github-trigger create-gitlab-server-trigger create-gitlab-trigger create-vbs-trigger delete get list update-bitbucket-cloud-trigger update-bitbucket-server-trigger update-devops-code-repo-trigger update-github-trigger update-gitlab-server-trigger update-gitlab-trigger update-vbs-trigger'
|
|
25
|
+
'devops trigger-dry-run-result' = 'trigger-deployment-dry-run trigger-deployment-dry-run-create-deploy-pipeline-deployment-details trigger-deployment-dry-run-create-deploy-pipeline-redeployment-details trigger-deployment-dry-run-create-single-deploy-stage-deployment-details trigger-deployment-dry-run-create-single-deploy-stage-redeployment-details'
|
|
25
26
|
'devops work-request' = 'get list'
|
|
26
27
|
'devops work-request-error' = 'list'
|
|
27
28
|
'devops work-request-log' = 'list'
|
|
@@ -256,6 +257,11 @@ function GetOciCommandsToLongParams_devops() {
|
|
|
256
257
|
'devops trigger update-gitlab-server-trigger' = 'actions defined-tags description display-name force freeform-tags from-json help if-match max-wait-seconds trigger-id wait-for-state wait-interval-seconds'
|
|
257
258
|
'devops trigger update-gitlab-trigger' = 'actions connection-id defined-tags description display-name force freeform-tags from-json help if-match max-wait-seconds trigger-id wait-for-state wait-interval-seconds'
|
|
258
259
|
'devops trigger update-vbs-trigger' = 'actions connection-id defined-tags description display-name force freeform-tags from-json help if-match max-wait-seconds trigger-id wait-for-state wait-interval-seconds'
|
|
260
|
+
'devops trigger-dry-run-result trigger-deployment-dry-run' = 'create-deployment-details from-json helm-diff-arguments help'
|
|
261
|
+
'devops trigger-dry-run-result trigger-deployment-dry-run-create-deploy-pipeline-deployment-details' = 'create-deployment-details-defined-tags create-deployment-details-deploy-artifact-override-arguments create-deployment-details-deploy-pipeline-id create-deployment-details-deploy-stage-override-arguments create-deployment-details-deployment-arguments create-deployment-details-display-name create-deployment-details-freeform-tags from-json helm-diff-arguments help'
|
|
262
|
+
'devops trigger-dry-run-result trigger-deployment-dry-run-create-deploy-pipeline-redeployment-details' = 'create-deployment-details-defined-tags create-deployment-details-deploy-pipeline-id create-deployment-details-display-name create-deployment-details-freeform-tags create-deployment-details-previous-deployment-id from-json helm-diff-arguments help'
|
|
263
|
+
'devops trigger-dry-run-result trigger-deployment-dry-run-create-single-deploy-stage-deployment-details' = 'create-deployment-details-defined-tags create-deployment-details-deploy-artifact-override-arguments create-deployment-details-deploy-pipeline-id create-deployment-details-deploy-stage-id create-deployment-details-deploy-stage-override-arguments create-deployment-details-deployment-arguments create-deployment-details-display-name create-deployment-details-freeform-tags from-json helm-diff-arguments help'
|
|
264
|
+
'devops trigger-dry-run-result trigger-deployment-dry-run-create-single-deploy-stage-redeployment-details' = 'create-deployment-details-defined-tags create-deployment-details-deploy-pipeline-id create-deployment-details-deploy-stage-id create-deployment-details-display-name create-deployment-details-freeform-tags create-deployment-details-previous-deployment-id from-json helm-diff-arguments help'
|
|
259
265
|
'devops work-request get' = 'from-json help work-request-id'
|
|
260
266
|
'devops work-request list' = 'all compartment-id from-json help limit operation-type-multi-value-query page page-size resource-id sort-by sort-order status work-request-id'
|
|
261
267
|
'devops work-request-error list' = 'all from-json help limit page page-size sort-by sort-order work-request-id'
|
|
@@ -491,6 +497,11 @@ function GetOciCommandsToShortParams_devops() {
|
|
|
491
497
|
'devops trigger update-gitlab-server-trigger' = '? h'
|
|
492
498
|
'devops trigger update-gitlab-trigger' = '? h'
|
|
493
499
|
'devops trigger update-vbs-trigger' = '? h'
|
|
500
|
+
'devops trigger-dry-run-result trigger-deployment-dry-run' = '? h'
|
|
501
|
+
'devops trigger-dry-run-result trigger-deployment-dry-run-create-deploy-pipeline-deployment-details' = '? h'
|
|
502
|
+
'devops trigger-dry-run-result trigger-deployment-dry-run-create-deploy-pipeline-redeployment-details' = '? h'
|
|
503
|
+
'devops trigger-dry-run-result trigger-deployment-dry-run-create-single-deploy-stage-deployment-details' = '? h'
|
|
504
|
+
'devops trigger-dry-run-result trigger-deployment-dry-run-create-single-deploy-stage-redeployment-details' = '? h'
|
|
494
505
|
'devops work-request get' = '? h'
|
|
495
506
|
'devops work-request list' = '? c h'
|
|
496
507
|
'devops work-request-error list' = '? h'
|
oci_cli/bin/streaming.psm1
CHANGED
|
@@ -32,11 +32,11 @@ function GetOciCommandsToLongParams_streaming() {
|
|
|
32
32
|
'streaming admin stream list' = 'all compartment-id from-json help id lifecycle-state limit name page page-size sort-by sort-order stream-pool-id'
|
|
33
33
|
'streaming admin stream update' = 'defined-tags force freeform-tags from-json help if-match max-wait-seconds stream-id stream-pool-id wait-for-state wait-interval-seconds'
|
|
34
34
|
'streaming admin stream-pool change-compartment' = 'compartment-id from-json help if-match stream-pool-id'
|
|
35
|
-
'streaming admin stream-pool create' = 'compartment-id custom-encryption-key-details defined-tags freeform-tags from-json help kafka-settings max-wait-seconds name private-endpoint-details wait-for-state wait-interval-seconds'
|
|
35
|
+
'streaming admin stream-pool create' = 'compartment-id custom-encryption-key-details defined-tags freeform-tags from-json help kafka-settings max-wait-seconds name private-endpoint-details security-attributes wait-for-state wait-interval-seconds'
|
|
36
36
|
'streaming admin stream-pool delete' = 'force from-json help if-match max-wait-seconds stream-pool-id wait-for-state wait-interval-seconds'
|
|
37
37
|
'streaming admin stream-pool get' = 'from-json help stream-pool-id'
|
|
38
38
|
'streaming admin stream-pool list' = 'all compartment-id from-json help id lifecycle-state limit name page page-size sort-by sort-order'
|
|
39
|
-
'streaming admin stream-pool update' = 'custom-encryption-key-details defined-tags force freeform-tags from-json help if-match kafka-settings max-wait-seconds name stream-pool-id wait-for-state wait-interval-seconds'
|
|
39
|
+
'streaming admin stream-pool update' = 'custom-encryption-key-details defined-tags force freeform-tags from-json help if-match kafka-settings max-wait-seconds name security-attributes stream-pool-id wait-for-state wait-interval-seconds'
|
|
40
40
|
'streaming stream cursor create-cursor' = 'from-json help offset partition stream-id time type'
|
|
41
41
|
'streaming stream cursor create-group-cursor' = 'commit-on-get from-json group-name help instance-name stream-id time timeout-in-ms type'
|
|
42
42
|
'streaming stream group commit' = 'cursor from-json help stream-id'
|
|
@@ -142,6 +142,23 @@ example of the JSON which must be provided. We recommend storing this
|
|
|
142
142
|
example in a file, modifying it as needed and then passing it back in
|
|
143
143
|
via the file:// syntax.
|
|
144
144
|
|
|
145
|
+
--job-storage-mount-configuration-override-details-list [complex type]
|
|
146
|
+
|
|
147
|
+
Collection of JobStorageMountConfigurationDetails.
|
|
148
|
+
|
|
149
|
+
This option is a JSON list with items of type
|
|
150
|
+
StorageMountConfigurationDetails. For documentation on
|
|
151
|
+
StorageMountConfigurationDetails please see our API reference: https:
|
|
152
|
+
//docs.cloud.oracle.com/api/#/en/datascience/20190101/datatypes/Stora
|
|
153
|
+
geMountConfigurationDetails. This is a complex type whose value must
|
|
154
|
+
be valid JSON. The value can be provided as a string on the command
|
|
155
|
+
line or passed in as a file 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
|
+
|
|
145
162
|
--log-configuration-override-details [complex type]
|
|
146
163
|
|
|
147
164
|
This is a complex type whose value must be valid JSON. The value can
|
|
@@ -148,6 +148,18 @@ via the file:// syntax.
|
|
|
148
148
|
The maximum time to wait for the resource to reach the lifecycle state
|
|
149
149
|
defined by "--wait-for-state". Defaults to 1200 seconds.
|
|
150
150
|
|
|
151
|
+
--parameters [complex type]
|
|
152
|
+
|
|
153
|
+
Parameters used in the pipeline. This is a complex type whose value
|
|
154
|
+
must be valid JSON. The value can be provided as a string on the
|
|
155
|
+
command line or passed in as a file using the file://path/to/file
|
|
156
|
+
syntax.
|
|
157
|
+
|
|
158
|
+
The "--generate-param-json-input" option can be used to generate an
|
|
159
|
+
example of the JSON which must be provided. We recommend storing this
|
|
160
|
+
example in a file, modifying it as needed and then passing it back in
|
|
161
|
+
via the file:// syntax.
|
|
162
|
+
|
|
151
163
|
--storage-mount-configuration-details-list [complex type]
|
|
152
164
|
|
|
153
165
|
The storage mount details to mount to the instance running the
|
|
@@ -144,6 +144,18 @@ via the file:// syntax.
|
|
|
144
144
|
The maximum time to wait for the resource to reach the lifecycle state
|
|
145
145
|
defined by "--wait-for-state". Defaults to 1200 seconds.
|
|
146
146
|
|
|
147
|
+
--parameters [complex type]
|
|
148
|
+
|
|
149
|
+
Parameters used in the pipeline. This is a complex type whose value
|
|
150
|
+
must be valid JSON. The value can be provided as a string on the
|
|
151
|
+
command line or passed in as a file using the file://path/to/file
|
|
152
|
+
syntax.
|
|
153
|
+
|
|
154
|
+
The "--generate-param-json-input" option can be used to generate an
|
|
155
|
+
example of the JSON which must be provided. We recommend storing this
|
|
156
|
+
example in a file, modifying it as needed and then passing it back in
|
|
157
|
+
via the file:// syntax.
|
|
158
|
+
|
|
147
159
|
--step-details [complex type]
|
|
148
160
|
|
|
149
161
|
Array of update details for each step. Only step configurations and
|
|
@@ -136,6 +136,18 @@ defined by "--wait-for-state". Defaults to 1200 seconds.
|
|
|
136
136
|
|
|
137
137
|
URL to fetch the Resource Principal Token from the parent resource.
|
|
138
138
|
|
|
139
|
+
--parameters-override [complex type]
|
|
140
|
+
|
|
141
|
+
Parameters override used in the pipeline run. This is a complex type
|
|
142
|
+
whose value must be valid JSON. The value can be provided as a string
|
|
143
|
+
on the command line or passed in as a file using the
|
|
144
|
+
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
|
+
|
|
139
151
|
--project-id [text]
|
|
140
152
|
|
|
141
153
|
The OCID of the project to associate the pipeline run with.
|
|
@@ -158,6 +170,24 @@ example of the JSON which must be provided. We recommend storing this
|
|
|
158
170
|
example in a file, modifying it as needed and then passing it back in
|
|
159
171
|
via the file:// syntax.
|
|
160
172
|
|
|
173
|
+
--storage-mount-configuration-override-details-list [complex type]
|
|
174
|
+
|
|
175
|
+
The storage mount override details to mount to the instance running
|
|
176
|
+
the pipeline step.
|
|
177
|
+
|
|
178
|
+
This option is a JSON list with items of type
|
|
179
|
+
StorageMountConfigurationDetails. For documentation on
|
|
180
|
+
StorageMountConfigurationDetails please see our API reference: https:
|
|
181
|
+
//docs.cloud.oracle.com/api/#/en/datascience/20190101/datatypes/Stora
|
|
182
|
+
geMountConfigurationDetails. This is a complex type whose value must
|
|
183
|
+
be valid JSON. The value can be provided as a string on the command
|
|
184
|
+
line or passed in as a file using the file://path/to/file syntax.
|
|
185
|
+
|
|
186
|
+
The "--generate-param-json-input" option can be used to generate an
|
|
187
|
+
example of the JSON which must be provided. We recommend storing this
|
|
188
|
+
example in a file, modifying it as needed and then passing it back in
|
|
189
|
+
via the file:// syntax.
|
|
190
|
+
|
|
161
191
|
--system-tags [complex type]
|
|
162
192
|
|
|
163
193
|
Usage of system tag keys. These predefined keys are scoped to
|
|
@@ -0,0 +1,174 @@
|
|
|
1
|
+
"trigger-deployment-dry-run-create-deploy-pipeline-deployment-details"
|
|
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
|
+
Sends a request to trigger a dry run, passing a
|
|
21
|
+
HelmDiffArgumentCollection This is an internal-only endpoint, access
|
|
22
|
+
to this endpoint is restricted. Any request from non-internal
|
|
23
|
+
tenancies will receive 403 Forbidden response.
|
|
24
|
+
|
|
25
|
+
|
|
26
|
+
Usage
|
|
27
|
+
=====
|
|
28
|
+
|
|
29
|
+
oci devops trigger-dry-run-result trigger-deployment-dry-run-create-deploy-pipeline-deployment-details [OPTIONS]
|
|
30
|
+
|
|
31
|
+
|
|
32
|
+
Required Parameters
|
|
33
|
+
===================
|
|
34
|
+
|
|
35
|
+
--create-deployment-details-deploy-pipeline-id [text]
|
|
36
|
+
|
|
37
|
+
The OCID of a pipeline.
|
|
38
|
+
|
|
39
|
+
--helm-diff-arguments [complex type]
|
|
40
|
+
|
|
41
|
+
This is a complex type whose value must be valid JSON. The value can
|
|
42
|
+
be provided as a string on the command line or passed in as a file
|
|
43
|
+
using the file://path/to/file syntax.
|
|
44
|
+
|
|
45
|
+
The "--generate-param-json-input" option can be used to generate an
|
|
46
|
+
example of the JSON which must be provided. We recommend storing this
|
|
47
|
+
example in a file, modifying it as needed and then passing it back in
|
|
48
|
+
via the file:// syntax.
|
|
49
|
+
|
|
50
|
+
|
|
51
|
+
Optional Parameters
|
|
52
|
+
===================
|
|
53
|
+
|
|
54
|
+
--create-deployment-details-defined-tags [complex type]
|
|
55
|
+
|
|
56
|
+
Defined tags for this resource. Each key is predefined and scoped to a
|
|
57
|
+
namespace. See Resource Tags. Example: *{“foo-namespace”: {“bar-key”:
|
|
58
|
+
“value”}}* This is a complex type whose value must be valid JSON. The
|
|
59
|
+
value can be provided as a string on the command line or passed in as
|
|
60
|
+
a file using the file://path/to/file syntax.
|
|
61
|
+
|
|
62
|
+
The "--generate-param-json-input" option can be used to generate an
|
|
63
|
+
example of the JSON which must be provided. We recommend storing this
|
|
64
|
+
example in a file, modifying it as needed and then passing it back in
|
|
65
|
+
via the file:// syntax.
|
|
66
|
+
|
|
67
|
+
--create-deployment-details-deploy-artifact-override-arguments [complex type]
|
|
68
|
+
|
|
69
|
+
This is a complex type whose value must be valid JSON. The value can
|
|
70
|
+
be provided as a string on the command line or passed in as a file
|
|
71
|
+
using the file://path/to/file syntax.
|
|
72
|
+
|
|
73
|
+
The "--generate-param-json-input" option can be used to generate an
|
|
74
|
+
example of the JSON which must be provided. We recommend storing this
|
|
75
|
+
example in a file, modifying it as needed and then passing it back in
|
|
76
|
+
via the file:// syntax.
|
|
77
|
+
|
|
78
|
+
--create-deployment-details-deploy-stage-override-arguments [complex type]
|
|
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
|
+
--create-deployment-details-deployment-arguments [complex type]
|
|
90
|
+
|
|
91
|
+
This is a complex type whose value must be valid JSON. The value can
|
|
92
|
+
be provided as a string on the command line or passed in as a file
|
|
93
|
+
using the file://path/to/file syntax.
|
|
94
|
+
|
|
95
|
+
The "--generate-param-json-input" option can be used to generate an
|
|
96
|
+
example of the JSON which must be provided. We recommend storing this
|
|
97
|
+
example in a file, modifying it as needed and then passing it back in
|
|
98
|
+
via the file:// syntax.
|
|
99
|
+
|
|
100
|
+
--create-deployment-details-display-name [text]
|
|
101
|
+
|
|
102
|
+
Deployment display name. Avoid entering confidential information.
|
|
103
|
+
|
|
104
|
+
--create-deployment-details-freeform-tags [complex type]
|
|
105
|
+
|
|
106
|
+
Simple key-value pair that is applied without any predefined name,
|
|
107
|
+
type or scope. Exists for cross-compatibility only. See Resource
|
|
108
|
+
Tags. Example: *{“bar-key”: “value”}* This is a complex type whose
|
|
109
|
+
value must be valid JSON. The value can be provided as a string on the
|
|
110
|
+
command line or passed in as a file using the file://path/to/file
|
|
111
|
+
syntax.
|
|
112
|
+
|
|
113
|
+
The "--generate-param-json-input" option can be used to generate an
|
|
114
|
+
example of the JSON which must be provided. We recommend storing this
|
|
115
|
+
example in a file, modifying it as needed and then passing it back in
|
|
116
|
+
via the file:// syntax.
|
|
117
|
+
|
|
118
|
+
--from-json [text]
|
|
119
|
+
|
|
120
|
+
Provide input to this command as a JSON document from a file using the
|
|
121
|
+
file://path-to/file syntax.
|
|
122
|
+
|
|
123
|
+
The "--generate-full-command-json-input" option can be used to
|
|
124
|
+
generate a sample json file to be used with this command option. The
|
|
125
|
+
key names are pre-populated and match the command option names
|
|
126
|
+
(converted to camelCase format, e.g. compartment-id –> compartmentId),
|
|
127
|
+
while the values of the keys need to be populated by the user before
|
|
128
|
+
using the sample file as an input to this command. For any command
|
|
129
|
+
option that accepts multiple values, the value of the key can be a
|
|
130
|
+
JSON array.
|
|
131
|
+
|
|
132
|
+
Options can still be provided on the command line. If an option exists
|
|
133
|
+
in both the JSON document and the command line then the command line
|
|
134
|
+
specified value will be used.
|
|
135
|
+
|
|
136
|
+
For examples on usage of this option, please see our “using CLI with
|
|
137
|
+
advanced JSON options” link: https://docs.cloud.oracle.com/iaas/Conte
|
|
138
|
+
nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
|
|
139
|
+
|
|
140
|
+
|
|
141
|
+
Global Parameters
|
|
142
|
+
=================
|
|
143
|
+
|
|
144
|
+
Use "oci --help" for help on global parameters.
|
|
145
|
+
|
|
146
|
+
"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
|
|
147
|
+
cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
|
|
148
|
+
defaults-file", "--endpoint", "--generate-full-command-json-input", "
|
|
149
|
+
--generate-param-json-input", "--help", "--latest-version", "--max-
|
|
150
|
+
retries", "--no-retry", "--opc-client-request-id", "--opc-request-id",
|
|
151
|
+
"--output", "--profile", "--proxy", "--query", "--raw-output", "--
|
|
152
|
+
read-timeout", "--realm-specific-endpoint", "--region", "--release-
|
|
153
|
+
info", "--request-id", "--version", "-?", "-d", "-h", "-i", "-v"
|
|
154
|
+
|
|
155
|
+
|
|
156
|
+
Example using required parameter
|
|
157
|
+
================================
|
|
158
|
+
|
|
159
|
+
Copy and paste the following example into a JSON file, replacing the
|
|
160
|
+
example parameters with your own.
|
|
161
|
+
|
|
162
|
+
oci devops trigger-dry-run-result trigger-deployment-dry-run-create-deploy-pipeline-deployment-details --generate-param-json-input helm-diff-arguments > helm-diff-arguments.json
|
|
163
|
+
|
|
164
|
+
Copy the following CLI commands into a file named example.sh. Run the
|
|
165
|
+
command by typing “bash example.sh” and replacing the example
|
|
166
|
+
parameters with your own.
|
|
167
|
+
|
|
168
|
+
Please note this sample will only work in the POSIX-compliant bash-
|
|
169
|
+
like shell. You need to set up the OCI configuration and appropriate
|
|
170
|
+
security policies before trying the examples.
|
|
171
|
+
|
|
172
|
+
export create_deployment_details_deploy_pipeline_id=<substitute-value-of-create_deployment_details_deploy_pipeline_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/devops/trigger-dry-run-result/trigger-deployment-dry-run-create-deploy-pipeline-deployment-details.html#cmdoption-create-deployment-details-deploy-pipeline-id
|
|
173
|
+
|
|
174
|
+
oci devops trigger-dry-run-result trigger-deployment-dry-run-create-deploy-pipeline-deployment-details --create-deployment-details-deploy-pipeline-id $create_deployment_details_deploy_pipeline_id --helm-diff-arguments file://helm-diff-arguments.json
|
|
@@ -0,0 +1,146 @@
|
|
|
1
|
+
"trigger-deployment-dry-run-create-deploy-pipeline-redeployment-details"
|
|
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
|
+
Sends a request to trigger a dry run, passing a
|
|
21
|
+
HelmDiffArgumentCollection This is an internal-only endpoint, access
|
|
22
|
+
to this endpoint is restricted. Any request from non-internal
|
|
23
|
+
tenancies will receive 403 Forbidden response.
|
|
24
|
+
|
|
25
|
+
|
|
26
|
+
Usage
|
|
27
|
+
=====
|
|
28
|
+
|
|
29
|
+
oci devops trigger-dry-run-result trigger-deployment-dry-run-create-deploy-pipeline-redeployment-details [OPTIONS]
|
|
30
|
+
|
|
31
|
+
|
|
32
|
+
Required Parameters
|
|
33
|
+
===================
|
|
34
|
+
|
|
35
|
+
--create-deployment-details-deploy-pipeline-id [text]
|
|
36
|
+
|
|
37
|
+
The OCID of a pipeline.
|
|
38
|
+
|
|
39
|
+
--create-deployment-details-previous-deployment-id [text]
|
|
40
|
+
|
|
41
|
+
Specifies the OCID of the previous deployment to be redeployed.
|
|
42
|
+
|
|
43
|
+
--helm-diff-arguments [complex type]
|
|
44
|
+
|
|
45
|
+
This is a complex type whose value must be valid JSON. The value can
|
|
46
|
+
be provided as a string on the command line or passed in as a file
|
|
47
|
+
using the file://path/to/file syntax.
|
|
48
|
+
|
|
49
|
+
The "--generate-param-json-input" option can be used to generate an
|
|
50
|
+
example of the JSON which must be provided. We recommend storing this
|
|
51
|
+
example in a file, modifying it as needed and then passing it back in
|
|
52
|
+
via the file:// syntax.
|
|
53
|
+
|
|
54
|
+
|
|
55
|
+
Optional Parameters
|
|
56
|
+
===================
|
|
57
|
+
|
|
58
|
+
--create-deployment-details-defined-tags [complex type]
|
|
59
|
+
|
|
60
|
+
Defined tags for this resource. Each key is predefined and scoped to a
|
|
61
|
+
namespace. See Resource Tags. Example: *{“foo-namespace”: {“bar-key”:
|
|
62
|
+
“value”}}* This is a complex type whose value must be valid JSON. The
|
|
63
|
+
value can be provided as a string on the command line or passed in as
|
|
64
|
+
a file using the file://path/to/file syntax.
|
|
65
|
+
|
|
66
|
+
The "--generate-param-json-input" option can be used to generate an
|
|
67
|
+
example of the JSON which must be provided. We recommend storing this
|
|
68
|
+
example in a file, modifying it as needed and then passing it back in
|
|
69
|
+
via the file:// syntax.
|
|
70
|
+
|
|
71
|
+
--create-deployment-details-display-name [text]
|
|
72
|
+
|
|
73
|
+
Deployment display name. Avoid entering confidential information.
|
|
74
|
+
|
|
75
|
+
--create-deployment-details-freeform-tags [complex type]
|
|
76
|
+
|
|
77
|
+
Simple key-value pair that is applied without any predefined name,
|
|
78
|
+
type or scope. Exists for cross-compatibility only. See Resource
|
|
79
|
+
Tags. Example: *{“bar-key”: “value”}* This is a complex type whose
|
|
80
|
+
value must be valid JSON. The value can be provided as a string on the
|
|
81
|
+
command line or passed in as a file using the file://path/to/file
|
|
82
|
+
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
|
+
|
|
112
|
+
Global Parameters
|
|
113
|
+
=================
|
|
114
|
+
|
|
115
|
+
Use "oci --help" for help on global parameters.
|
|
116
|
+
|
|
117
|
+
"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
|
|
118
|
+
cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
|
|
119
|
+
defaults-file", "--endpoint", "--generate-full-command-json-input", "
|
|
120
|
+
--generate-param-json-input", "--help", "--latest-version", "--max-
|
|
121
|
+
retries", "--no-retry", "--opc-client-request-id", "--opc-request-id",
|
|
122
|
+
"--output", "--profile", "--proxy", "--query", "--raw-output", "--
|
|
123
|
+
read-timeout", "--realm-specific-endpoint", "--region", "--release-
|
|
124
|
+
info", "--request-id", "--version", "-?", "-d", "-h", "-i", "-v"
|
|
125
|
+
|
|
126
|
+
|
|
127
|
+
Example using required parameter
|
|
128
|
+
================================
|
|
129
|
+
|
|
130
|
+
Copy and paste the following example into a JSON file, replacing the
|
|
131
|
+
example parameters with your own.
|
|
132
|
+
|
|
133
|
+
oci devops trigger-dry-run-result trigger-deployment-dry-run-create-deploy-pipeline-redeployment-details --generate-param-json-input helm-diff-arguments > helm-diff-arguments.json
|
|
134
|
+
|
|
135
|
+
Copy the following CLI commands into a file named example.sh. Run the
|
|
136
|
+
command by typing “bash example.sh” and replacing the example
|
|
137
|
+
parameters with your own.
|
|
138
|
+
|
|
139
|
+
Please note this sample will only work in the POSIX-compliant bash-
|
|
140
|
+
like shell. You need to set up the OCI configuration and appropriate
|
|
141
|
+
security policies before trying the examples.
|
|
142
|
+
|
|
143
|
+
export create_deployment_details_deploy_pipeline_id=<substitute-value-of-create_deployment_details_deploy_pipeline_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/devops/trigger-dry-run-result/trigger-deployment-dry-run-create-deploy-pipeline-redeployment-details.html#cmdoption-create-deployment-details-deploy-pipeline-id
|
|
144
|
+
export create_deployment_details_previous_deployment_id=<substitute-value-of-create_deployment_details_previous_deployment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/devops/trigger-dry-run-result/trigger-deployment-dry-run-create-deploy-pipeline-redeployment-details.html#cmdoption-create-deployment-details-previous-deployment-id
|
|
145
|
+
|
|
146
|
+
oci devops trigger-dry-run-result trigger-deployment-dry-run-create-deploy-pipeline-redeployment-details --create-deployment-details-deploy-pipeline-id $create_deployment_details_deploy_pipeline_id --create-deployment-details-previous-deployment-id $create_deployment_details_previous_deployment_id --helm-diff-arguments file://helm-diff-arguments.json
|