oci-cli 3.66.1__py3-none-any.whl → 3.67.0__py3-none-any.whl

oci_cli/help_text_producer/data_files/text/cmdref/jms/container-summary.txt

@@ -0,0 +1,14 @@
+container-summary
+*****************
+
+
+Description
+===========
+
+Information about a container in the cluster.
+
+
+Available Commands
+==================
+
+* list-containers

oci_cli/help_text_producer/data_files/text/cmdref/jms/export-setting/update.txt

@@ -41,6 +41,17 @@ ExportSetting flag to store enabled or disabled status.
 Optional Parameters
 ===================
 
+--export-data-filters [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.
+
 --export-duration [text]
 
 The duration of data to be exported for fleets.
@@ -65,6 +76,10 @@ Accepted values are:
 
    MANAGED_INSTANCE, MANAGED_INSTANCE_PLUS_JAVA_RUNTIME, MANAGED_INSTANCE_PLUS_JAVA_RUNTIME_PLUS_APPLICATION
 
+--force
+
+Perform update without prompting for confirmation.
+
 --from-json [text]
 
 Provide input to this command as a JSON document from a file using the

oci_cli/help_text_producer/data_files/text/cmdref/jms/fleet-agent-configuration/update.txt

@@ -75,6 +75,10 @@ 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.
 
+--is-capturing-ip-address-and-fqdn-enabled [boolean]
+
+Collect network addresses of managed instances in the fleet.
+
 --is-collecting-managed-instance-metrics-enabled [boolean]
 
 Collect JMS agent metrics on all managed instances in the fleet.
@@ -84,6 +88,10 @@ Collect JMS agent metrics on all managed instances in the fleet.
 Collect username for application invocations for all managed instances
 in the fleet.
 
+--is-libraries-scan-enabled [boolean]
+
+Enable libraries scan on all managed instances in the fleet.
+
 --jre-scan-frequency [integer]
 
 The frequency (in minutes) of JRE scanning. (That is, how often should

oci_cli/help_text_producer/data_files/text/cmdref/jms/installation-usage/summarize.txt

@@ -127,7 +127,7 @@ specified _timeLastSeen_ is default.
 
 Accepted values are:
 
-   approximateApplicationCount, approximateManagedInstanceCount, jreDistribution, jreVendor, jreVersion, osName, path, timeFirstSeen, timeLastSeen
+   approximateApplicationCount, approximateManagedInstanceCount, jreDistribution, jreVendor, jreVersion, osName, path, securityStatus, timeFirstSeen, timeLastSeen
 
 --sort-order [text]
 

oci_cli/help_text_producer/data_files/text/cmdref/jms/jms-plugin/create.txt

@@ -35,17 +35,26 @@ Required Parameters
 
 --agent-id [text]
 
-The OCID of the Management Agent (OMA) or the Oracle Cloud Agent (OCA)
-instance where the JMS plugin is deployed.
+The OCID of the Management Agent (OMA), the Oracle Cloud Agent (OCA),
+or the Oracle Container Management Agent (OCMA) instance where the JMS
+plugin is deployed.
 
 --compartment-id, -c [text]
 
-The OMA/OCA agent’s compartment OCID.
+The OMA/OCA/OCMA agent’s compartment OCID.
 
 
 Optional Parameters
 ===================
 
+--agent-type [text]
+
+The agent type.
+
+Accepted values are:
+
+   OCA, OCMA, OMA
+
 --defined-tags [complex type]
 
 Defined tags for this resource. Each key is predefined and scoped to a

oci_cli/help_text_producer/data_files/text/cmdref/jms/jms-plugin/list.txt

@@ -29,8 +29,8 @@ Optional Parameters
 
 --agent-id [text]
 
-The ManagementAgent (OMA) or Instance (OCA) OCID that identifies the
-Agent.
+The ManagementAgent (OMA), Oracle Cloud Agent (OCA), or the Oracle
+Container Management Agent (OCMA) OCID that identifies the Agent.
 
 --agent-type [text]
 
@@ -38,7 +38,7 @@ Filter JmsPlugin with agent type.
 
 Accepted values are:
 
-   OCA, OMA
+   OCA, OCMA, OMA
 
 --all
 

oci_cli/help_text_producer/data_files/text/cmdref/jms/library-application-usage-summary/list-library-application-usage.txt

@@ -0,0 +1,332 @@
+"list-library-application-usage"
+********************************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+List applications where a library has been detected filtered by query
+parameters.
+
+
+Usage
+=====
+
+   oci jms library-application-usage-summary list-library-application-usage [OPTIONS]
+
+
+Required Parameters
+===================
+
+--fleet-id [text]
+
+The OCID of the Fleet.
+
+--library-key [text]
+
+The unique identifier of a Java library.
+
+
+Optional Parameters
+===================
+
+--all
+
+Fetches all pages of results. If you provide this option, then you
+cannot provide the "--limit" option.
+
+--application-id [text]
+
+The Fleet-unique identifier of the application.
+
+--application-name [text]
+
+The name of the application.
+
+--application-name-contains [text]
+
+Filter the list with application name contains the given value.
+
+--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.
+
+--managed-instance-id [text]
+
+The Fleet-unique identifier of the managed instance.
+
+--page [text]
+
+The page token representing the page at which to start retrieving
+results. The token is usually retrieved from a previous list call.
+
+--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.
+
+--sort-by [text]
+
+The field to sort library application usage summaries.  Only one sort
+order may be provided. If no value is specified _lastSeenInClasspath_
+is default.
+
+Accepted values are:
+
+   applicationName, firstSeenInClasspath, lastDetectedDynamically, lastSeenInClasspath, managedInstanceCount
+
+--sort-order [text]
+
+The sort order, either ‘asc’ or ‘desc’.
+
+Accepted values are:
+
+   ASC, DESC
+
+--time-end [datetime]
+
+The end of the time period during which resources are searched
+(formatted according to RFC3339).
+
+   The following datetime formats are supported:
+
+
+UTC with microseconds
+---------------------
+
+   Format: YYYY-MM-DDTHH:mm:ss.ssssssTZD
+   Example: 2017-09-15T20:30:00.123456Z
+
+   UTC with milliseconds
+   ***********************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ss.sssTZD
+       Example: 2017-09-15T20:30:00.123Z
+
+   UTC without milliseconds
+   **************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ssTZD
+       Example: 2017-09-15T20:30:00Z
+
+   UTC with minute precision
+   **************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mmTZD
+       Example: 2017-09-15T20:30Z
+
+
+Timezone with microseconds
+--------------------------
+
+   Format: YYYY-MM-DDTHH:mm:ssTZD
+   Example: 2017-09-15T12:30:00.456789-08:00, 2017-09-15T12:30:00.456789-0800
+
+   Timezone with milliseconds
+   ***************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ssTZD
+       Example: 2017-09-15T12:30:00.456-08:00, 2017-09-15T12:30:00.456-0800
+
+   Timezone without milliseconds
+   *******************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ssTZD
+       Example: 2017-09-15T12:30:00-08:00, 2017-09-15T12:30:00-0800
+
+   Timezone with minute precision
+   *******************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mmTZD
+       Example: 2017-09-15T12:30-08:00, 2017-09-15T12:30-0800
+
+   Short date and time
+   ********************
+   The timezone for this date and time will be taken as UTC (Needs to be surrounded by single or double quotes)
+
+   .. code::
+
+       Format: 'YYYY-MM-DD HH:mm' or "YYYY-MM-DD HH:mm"
+       Example: '2017-09-15 17:25'
+
+   Date Only
+   **********
+   This date will be taken as midnight UTC of that day
+
+   .. code::
+
+       Format: YYYY-MM-DD
+       Example: 2017-09-15
+
+   Epoch seconds
+   **************
+   .. code::
+
+       Example: 1412195400
+
+--time-start [datetime]
+
+The start of the time period during which resources are searched
+(formatted according to RFC3339).
+
+   The following datetime formats are supported:
+
+
+UTC with microseconds
+---------------------
+
+   Format: YYYY-MM-DDTHH:mm:ss.ssssssTZD
+   Example: 2017-09-15T20:30:00.123456Z
+
+   UTC with milliseconds
+   ***********************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ss.sssTZD
+       Example: 2017-09-15T20:30:00.123Z
+
+   UTC without milliseconds
+   **************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ssTZD
+       Example: 2017-09-15T20:30:00Z
+
+   UTC with minute precision
+   **************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mmTZD
+       Example: 2017-09-15T20:30Z
+
+
+Timezone with microseconds
+--------------------------
+
+   Format: YYYY-MM-DDTHH:mm:ssTZD
+   Example: 2017-09-15T12:30:00.456789-08:00, 2017-09-15T12:30:00.456789-0800
+
+   Timezone with milliseconds
+   ***************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ssTZD
+       Example: 2017-09-15T12:30:00.456-08:00, 2017-09-15T12:30:00.456-0800
+
+   Timezone without milliseconds
+   *******************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mm:ssTZD
+       Example: 2017-09-15T12:30:00-08:00, 2017-09-15T12:30:00-0800
+
+   Timezone with minute precision
+   *******************************
+   .. code::
+
+       Format: YYYY-MM-DDTHH:mmTZD
+       Example: 2017-09-15T12:30-08:00, 2017-09-15T12:30-0800
+
+   Short date and time
+   ********************
+   The timezone for this date and time will be taken as UTC (Needs to be surrounded by single or double quotes)
+
+   .. code::
+
+       Format: 'YYYY-MM-DD HH:mm' or "YYYY-MM-DD HH:mm"
+       Example: '2017-09-15 17:25'
+
+   Date Only
+   **********
+   This date will be taken as midnight UTC of that day
+
+   .. code::
+
+       Format: YYYY-MM-DD
+       Example: 2017-09-15
+
+   Epoch seconds
+   **************
+   .. code::
+
+       Example: 1412195400
+
+
+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 jms fleet create --generate-param-json-input inventory-log > inventory-log.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/jms/fleet/create.html#cmdoption-compartment-id
+       export display_name=<substitute-value-of-display_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/jms/fleet/create.html#cmdoption-display-name
+       export library_key=<substitute-value-of-library_key> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/jms/library-application-usage-summary/list-library-application-usage.html#cmdoption-library-key
+
+       fleet_id=$(oci jms fleet create --compartment-id $compartment_id --display-name $display_name --inventory-log file://inventory-log.json --query data.id --raw-output)
+
+       oci jms library-application-usage-summary list-library-application-usage --fleet-id $fleet_id --library-key $library_key

oci_cli/help_text_producer/data_files/text/cmdref/jms/library-application-usage-summary.txt

@@ -0,0 +1,16 @@
+library-application-usage-summary
+*********************************
+
+
+Description
+===========
+
+Summary of an application where a given library was detected
+statically and/or dynamically. Contains the count of managed instances
+where the library was detected with this application.
+
+
+Available Commands
+==================
+
+* list-library-application-usage