oci-cli 3.70.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/report-metadata-collection/list-report-metadata.txt

@@ -0,0 +1,133 @@
+"list-report-metadata"
+**********************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Returns a list of all the report metadata.
+
+
+Usage
+=====
+
+   oci fleet-apps-management fleet-apps-management-operations report-metadata-collection list-report-metadata [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.
+
+--report-name [text]
+
+A filter to return data for given report name.
+
+--sort-by [text]
+
+The field to sort by. Only one sort order may be provided. Default
+order for timeCreated is descending. Default order for displayName is
+ascending.
+
+Accepted values are:
+
+   displayName, timeCreated
+
+--sort-order [text]
+
+The sort order to use, either ‘ASC’ or ‘DESC’.
+
+Accepted values are:
+
+   ASC, DESC
+
+
+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/report-metadata-collection/list-report-metadata.html#cmdoption-compartment-id
+
+       oci fleet-apps-management fleet-apps-management-operations report-metadata-collection list-report-metadata --compartment-id $compartment_id

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

@@ -0,0 +1,14 @@
+report-metadata-collection
+**************************
+
+
+Description
+===========
+
+Results of a run report .
+
+
+Available Commands
+==================
+
+* list-report-metadata

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet-apps-management-operations/scheduler-execution-collection/list-scheduler-executions.txt

@@ -15,7 +15,7 @@
 Description
 ===========
 
-Returns a list of all Fleets that are scheduled.
+Returns a list of all executions that are scheduled.
 
 
 Usage
@@ -37,6 +37,13 @@ cannot provide the "--limit" option.
 The ID of the compartment in which to list resources. Empty only if
 the resource OCID query param is not specified.
 
+--compartment-id-in-subtree [boolean]
+
+If set to true, resources will be returned for not only the provided
+compartment, but all compartments which descend from it. Which
+resources are returned and their field contents depends on the value
+of accessLevel.
+
 --display-name [text]
 
 A filter to return only resources that match the entire display name
@@ -64,6 +71,11 @@ 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
 
+--lifecycle-operation [text]
+
+A filter to return only resources their lifecycleOperation matches the
+given lifecycleOperation.
+
 --limit [integer]
 
 The maximum number of items to return.

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