oci-cli 3.69.0__py3-none-any.whl → 3.70.1__py3-none-any.whl

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet-apps-management-operations/target-component-collection/list-target-components.txt

@@ -0,0 +1,147 @@
+"list-target-components"
+************************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Gets a list of target component.
+
+
+Usage
+=====
+
+   oci fleet-apps-management fleet-apps-management-operations target-component-collection list-target-components [OPTIONS]
+
+
+Required Parameters
+===================
+
+--compartment-id, -c [text]
+
+The ID of the compartment in which to list resources.
+
+
+Optional Parameters
+===================
+
+--all
+
+Fetches all pages of results. If you provide this option, then you
+cannot provide the "--limit" option.
+
+--from-json [text]
+
+Provide input to this command as a JSON document from a file using the
+file://path-to/file syntax.
+
+The "--generate-full-command-json-input" option can be used to
+generate a sample json file to be used with this command option. The
+key names are pre-populated and match the command option names
+(converted to camelCase format, e.g. compartment-id –> compartmentId),
+while the values of the keys need to be populated by the user before
+using the sample file as an input to this command. For any command
+option that accepts multiple values, the value of the key can be a
+JSON array.
+
+Options can still be provided on the command line. If an option exists
+in both the JSON document and the command line then the command line
+specified value will be used.
+
+For examples on usage of this option, please see our “using CLI with
+advanced JSON options” link: https://docs.cloud.oracle.com/iaas/Conte
+nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
+
+--limit [integer]
+
+The maximum number of items to return.
+
+--name [text]
+
+Target Component Name.
+
+--page [text]
+
+A token representing the position at which to start retrieving
+results. This must come from the *opc-next-page* header field of a
+previous response.
+
+--page-size [integer]
+
+When fetching results, the number of results to fetch per call. Only
+valid when used with "--all" or "--limit", and ignored otherwise.
+
+--severity [text]
+
+Patch severity.
+
+Accepted values are:
+
+   CRITICAL, HIGH, LOW, MEDIUM
+
+--sort-by [text]
+
+The field to sort by. Only one sort order may be provided.
+
+Accepted values are:
+
+   componentName
+
+--sort-order [text]
+
+The sort order to use, either ‘ASC’ or ‘DESC’.
+
+Accepted values are:
+
+   ASC, DESC
+
+--target-id [text]
+
+Target Id.
+
+--target-name [text]
+
+Target name.
+
+
+Global Parameters
+=================
+
+Use "oci --help" for help on global parameters.
+
+"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
+cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
+defaults-file", "--endpoint", "--generate-full-command-json-input", "
+--generate-param-json-input", "--help", "--latest-version", "--max-
+retries", "--no-retry", "--opc-client-request-id", "--opc-request-id",
+"--output", "--profile", "--proxy", "--query", "--raw-output", "--
+read-timeout", "--realm-specific-endpoint", "--region", "--release-
+info", "--request-id", "--version", "-?", "-d", "-h", "-i", "-v"
+
+
+Example using required parameter
+================================
+
+Copy the following CLI commands into a file named example.sh. Run the
+command by typing “bash example.sh” and replacing the example
+parameters with your own.
+
+Please note this sample will only work in the POSIX-compliant bash-
+like shell. You need to set up the OCI configuration and appropriate
+security policies before trying the examples.
+
+       export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-apps-management/fleet-apps-management-operations/target-component-collection/list-target-components.html#cmdoption-compartment-id
+
+       oci fleet-apps-management fleet-apps-management-operations target-component-collection list-target-components --compartment-id $compartment_id

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet-apps-management-operations/target-component-collection.txt

@@ -0,0 +1,14 @@
+target-component-collection
+***************************
+
+
+Description
+===========
+
+Results of an target component search.
+
+
+Available Commands
+==================
+
+* list-target-components

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet-apps-management-operations/target-property-collection/list-target-properties.txt

@@ -0,0 +1,143 @@
+"list-target-properties"
+************************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Gets a list of target properties.
+
+
+Usage
+=====
+
+   oci fleet-apps-management fleet-apps-management-operations target-property-collection list-target-properties [OPTIONS]
+
+
+Required Parameters
+===================
+
+--compartment-id, -c [text]
+
+The ID of the compartment in which to list resources.
+
+
+Optional Parameters
+===================
+
+--all
+
+Fetches all pages of results. If you provide this option, then you
+cannot provide the "--limit" option.
+
+--from-json [text]
+
+Provide input to this command as a JSON document from a file using the
+file://path-to/file syntax.
+
+The "--generate-full-command-json-input" option can be used to
+generate a sample json file to be used with this command option. The
+key names are pre-populated and match the command option names
+(converted to camelCase format, e.g. compartment-id –> compartmentId),
+while the values of the keys need to be populated by the user before
+using the sample file as an input to this command. For any command
+option that accepts multiple values, the value of the key can be a
+JSON array.
+
+Options can still be provided on the command line. If an option exists
+in both the JSON document and the command line then the command line
+specified value will be used.
+
+For examples on usage of this option, please see our “using CLI with
+advanced JSON options” link: https://docs.cloud.oracle.com/iaas/Conte
+nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
+
+--limit [integer]
+
+The maximum number of items to return.
+
+--page [text]
+
+A token representing the position at which to start retrieving
+results. This must come from the *opc-next-page* header field of a
+previous response.
+
+--page-size [integer]
+
+When fetching results, the number of results to fetch per call. Only
+valid when used with "--all" or "--limit", and ignored otherwise.
+
+--severity [text]
+
+Patch severity.
+
+Accepted values are:
+
+   CRITICAL, HIGH, LOW, MEDIUM
+
+--sort-by [text]
+
+The field to sort by. Only one sort order may be provided.
+
+Accepted values are:
+
+   propertyName
+
+--sort-order [text]
+
+The sort order to use, either ‘ASC’ or ‘DESC’.
+
+Accepted values are:
+
+   ASC, DESC
+
+--target-id [text]
+
+Target Id.
+
+--target-name [text]
+
+Target name.
+
+
+Global Parameters
+=================
+
+Use "oci --help" for help on global parameters.
+
+"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
+cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
+defaults-file", "--endpoint", "--generate-full-command-json-input", "
+--generate-param-json-input", "--help", "--latest-version", "--max-
+retries", "--no-retry", "--opc-client-request-id", "--opc-request-id",
+"--output", "--profile", "--proxy", "--query", "--raw-output", "--
+read-timeout", "--realm-specific-endpoint", "--region", "--release-
+info", "--request-id", "--version", "-?", "-d", "-h", "-i", "-v"
+
+
+Example using required parameter
+================================
+
+Copy the following CLI commands into a file named example.sh. Run the
+command by typing “bash example.sh” and replacing the example
+parameters with your own.
+
+Please note this sample will only work in the POSIX-compliant bash-
+like shell. You need to set up the OCI configuration and appropriate
+security policies before trying the examples.
+
+       export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-apps-management/fleet-apps-management-operations/target-property-collection/list-target-properties.html#cmdoption-compartment-id
+
+       oci fleet-apps-management fleet-apps-management-operations target-property-collection list-target-properties --compartment-id $compartment_id

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet-apps-management-operations/target-property-collection.txt

@@ -0,0 +1,14 @@
+target-property-collection
+**************************
+
+
+Description
+===========
+
+Results of an target property search.
+
+
+Available Commands
+==================
+
+* list-target-properties

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet-apps-management-operations.txt

@@ -33,6 +33,10 @@ Available Commands
 
   * list-executions
 
+* installed-patch-collection
+
+  * list-installed-patches
+
 * inventory-record-collection
 
   * list-inventory-records
@@ -69,6 +73,18 @@ Available Commands
 
   * list-patches
 
+* recommended-patch-collection
+
+  * list-recommended-patches
+
+* report-collection
+
+  * report
+
+* report-metadata-collection
+
+  * list-report-metadata
+
 * resource-collection
 
   * list-resources
@@ -128,3 +144,11 @@ Available Commands
 * step-collection
 
   * list-steps
+
+* target-component-collection
+
+  * list-target-components
+
+* target-property-collection
+
+  * list-target-properties

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet-apps-management-runbooks/import-runbook-details/import-runbook.txt

@@ -0,0 +1,187 @@
+"import-runbook"
+****************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Import the specified version of the runbook.
+
+
+Usage
+=====
+
+   oci fleet-apps-management fleet-apps-management-runbooks import-runbook-details import-runbook [OPTIONS]
+
+
+Required Parameters
+===================
+
+--compartment-id, -c [text]
+
+OCID of the compartment to which the resource belongs to.
+
+--content-destination [complex type]
+
+This is a complex type whose value must be valid JSON. The value can
+be provided as a string on the command line or passed in as a file
+using the file://path/to/file syntax.
+
+The "--generate-param-json-input" option can be used to generate an
+example of the JSON which must be provided. We recommend storing this
+example in a file, modifying it as needed and then passing it back in
+via the file:// syntax.
+
+--content-source [complex type]
+
+This is a complex type whose value must be valid JSON. The value can
+be provided as a string on the command line or passed in as a file
+using the file://path/to/file syntax.
+
+The "--generate-param-json-input" option can be used to generate an
+example of the JSON which must be provided. We recommend storing this
+example in a file, modifying it as needed and then passing it back in
+via the file:// syntax.
+
+
+Optional Parameters
+===================
+
+--from-json [text]
+
+Provide input to this command as a JSON document from a file using the
+file://path-to/file syntax.
+
+The "--generate-full-command-json-input" option can be used to
+generate a sample json file to be used with this command option. The
+key names are pre-populated and match the command option names
+(converted to camelCase format, e.g. compartment-id –> compartmentId),
+while the values of the keys need to be populated by the user before
+using the sample file as an input to this command. For any command
+option that accepts multiple values, the value of the key can be a
+JSON array.
+
+Options can still be provided on the command line. If an option exists
+in both the JSON document and the command line then the command line
+specified value will be used.
+
+For examples on usage of this option, please see our “using CLI with
+advanced JSON options” link: https://docs.cloud.oracle.com/iaas/Conte
+nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
+
+--if-match [text]
+
+For optimistic concurrency control. In the PUT or DELETE call for a
+resource, set the *if-match* parameter to the value of the etag from a
+previous GET or POST response for that resource. The resource will be
+updated or deleted only if the etag you provide matches the resource’s
+current etag value.
+
+--import-option [text]
+
+ImportOptions for Runbook.
+
+Accepted values are:
+
+   INCREMENT, REPLACE, RETAIN
+
+--max-wait-seconds [integer]
+
+The maximum time to wait for the work request to reach the state
+defined by "--wait-for-state". Defaults to 1200 seconds.
+
+--required-values [complex type]
+
+List of required values.
+
+This option is a JSON list with items of type
+RunbookImportRequiredValue.  For documentation on
+RunbookImportRequiredValue please see our API reference: https://docs
+.cloud.oracle.com/api/#/en/fleetappsmanagementrunbooks/20250228/datat
+ypes/RunbookImportRequiredValue. This is a complex type whose value
+must be valid JSON. The value can be provided as a string on the
+command line or passed in as a file using the file://path/to/file
+syntax.
+
+The "--generate-param-json-input" option can be used to generate an
+example of the JSON which must be provided. We recommend storing this
+example in a file, modifying it as needed and then passing it back in
+via the file:// syntax.
+
+--runbook-name [text]
+
+The name of the runbook.
+
+--version-parameterconflict [text]
+
+Version number.
+
+--wait-for-state [text]
+
+This operation asynchronously creates, modifies or deletes a resource
+and uses a work request to track the progress of the operation.
+Specify this option to perform the action and then wait until the work
+request reaches a certain state. Multiple states can be specified,
+returning on the first state. For example, "--wait-for-state"
+SUCCEEDED "--wait-for-state" FAILED would return on whichever
+lifecycle state is reached first. If timeout is reached, a return code
+of 2 is returned. For any other error, a return code of 1 is returned.
+
+Accepted values are:
+
+   ACCEPTED, CANCELED, CANCELING, FAILED, IN_PROGRESS, NEEDS_ATTENTION, SUCCEEDED, WAITING
+
+--wait-interval-seconds [integer]
+
+Check every "--wait-interval-seconds" to see whether the work request
+has reached the state defined by "--wait-for-state". Defaults to 30
+seconds.
+
+
+Global Parameters
+=================
+
+Use "oci --help" for help on global parameters.
+
+"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
+cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
+defaults-file", "--endpoint", "--generate-full-command-json-input", "
+--generate-param-json-input", "--help", "--latest-version", "--max-
+retries", "--no-retry", "--opc-client-request-id", "--opc-request-id",
+"--output", "--profile", "--proxy", "--query", "--raw-output", "--
+read-timeout", "--realm-specific-endpoint", "--region", "--release-
+info", "--request-id", "--version", "-?", "-d", "-h", "-i", "-v"
+
+
+Example using required parameter
+================================
+
+Copy and paste the following example into a JSON file, replacing the
+example parameters with your own.
+
+       oci fleet-apps-management fleet-apps-management-runbooks import-runbook-details import-runbook --generate-param-json-input content-destination > content-destination.json
+       oci fleet-apps-management fleet-apps-management-runbooks import-runbook-details import-runbook --generate-param-json-input content-source > content-source.json
+
+Copy the following CLI commands into a file named example.sh. Run the
+command by typing “bash example.sh” and replacing the example
+parameters with your own.
+
+Please note this sample will only work in the POSIX-compliant bash-
+like shell. You need to set up the OCI configuration and appropriate
+security policies before trying the examples.
+
+       export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-apps-management/fleet-apps-management-runbooks/import-runbook-details/import-runbook.html#cmdoption-compartment-id
+
+       oci fleet-apps-management fleet-apps-management-runbooks import-runbook-details import-runbook --compartment-id $compartment_id --content-destination file://content-destination.json --content-source file://content-source.json

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet-apps-management-runbooks/import-runbook-details.txt

@@ -0,0 +1,14 @@
+import-runbook-details
+**********************
+
+
+Description
+===========
+
+Request to Import Runbook.
+
+
+Available Commands
+==================
+
+* import-runbook