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-admin/platform-configuration/update-platform-configuration-product-config-category-details.txt

@@ -120,6 +120,19 @@ 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.
 
+--defined-tags [complex type]
+
+Defined tags for this resource. Each key is predefined and scoped to a
+namespace. Example: *{“foo-namespace”: {“bar-key”: “value”}}* 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.
+
 --description [text]
 
 A user-friendly description. To provide some insight about the
@@ -134,6 +147,23 @@ Example:
 
    My new resource
 
+--force
+
+Perform update without prompting for confirmation.
+
+--freeform-tags [complex type]
+
+Simple key-value pair that is applied without any predefined name,
+type or scope. Exists for cross-compatibility only. Example: *{“bar-
+key”: “value”}* 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.
+
 --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/fleet-apps-management/fleet-apps-management-admin/platform-configuration/update-platform-configuration-product-stack-config-category-details.txt

@@ -61,6 +61,19 @@ 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.
 
+--defined-tags [complex type]
+
+Defined tags for this resource. Each key is predefined and scoped to a
+namespace. Example: *{“foo-namespace”: {“bar-key”: “value”}}* 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.
+
 --description [text]
 
 A user-friendly description. To provide some insight about the
@@ -75,6 +88,23 @@ Example:
 
    My new resource
 
+--force
+
+Perform update without prompting for confirmation.
+
+--freeform-tags [complex type]
+
+Simple key-value pair that is applied without any predefined name,
+type or scope. Exists for cross-compatibility only. Example: *{“bar-
+key”: “value”}* 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.
+
 --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/fleet-apps-management/fleet-apps-management-admin/platform-configuration/update-platform-configuration-self-hosted-instance-config-category-details.txt

@@ -50,6 +50,19 @@ Example:
 
    My new resource
 
+--defined-tags [complex type]
+
+Defined tags for this resource. Each key is predefined and scoped to a
+namespace. Example: *{“foo-namespace”: {“bar-key”: “value”}}* 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.
+
 --description [text]
 
 A user-friendly description. To provide some insight about the
@@ -64,6 +77,23 @@ Example:
 
    My new resource
 
+--force
+
+Perform update without prompting for confirmation.
+
+--freeform-tags [complex type]
+
+Simple key-value pair that is applied without any predefined name,
+type or scope. Exists for cross-compatibility only. Example: *{“bar-
+key”: “value”}* 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.
+
 --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/fleet-apps-management/fleet-apps-management-admin/platform-configuration/update.txt

@@ -48,6 +48,19 @@ 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.
 
+--defined-tags [complex type]
+
+Defined tags for this resource. Each key is predefined and scoped to a
+namespace. Example: *{“foo-namespace”: {“bar-key”: “value”}}* 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.
+
 --description [text]
 
 A user-friendly description. To provide some insight about the
@@ -66,6 +79,19 @@ Example:
 
 Perform update without prompting for confirmation.
 
+--freeform-tags [complex type]
+
+Simple key-value pair that is applied without any predefined name,
+type or scope. Exists for cross-compatibility only. Example: *{“bar-
+key”: “value”}* 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.
+
 --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/fleet-apps-management/fleet-apps-management-admin/platform-configuration-collection/list-platform-configurations.txt

@@ -93,7 +93,7 @@ given lifecycleState.
 
 Accepted values are:
 
-   ACTIVE, CREATING, DELETED, DELETING, FAILED, UPDATING
+   ACTIVE, CREATING, DELETED, DELETING, FAILED, INACTIVE, UPDATING
 
 --limit [integer]
 

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet-apps-management-admin/property/create.txt

@@ -63,6 +63,32 @@ Accepted values are:
 Optional Parameters
 ===================
 
+--defined-tags [complex type]
+
+Defined tags for this resource. Each key is predefined and scoped to a
+namespace. Example: *{“foo-namespace”: {“bar-key”: “value”}}* 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.
+
+--freeform-tags [complex type]
+
+Simple key-value pair that is applied without any predefined name,
+type or scope. Exists for cross-compatibility only. Example: *{“bar-
+key”: “value”}* 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.
+
 --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/fleet-apps-management/fleet-apps-management-admin/property/update.txt

@@ -37,6 +37,19 @@ unique Property identifier
 Optional Parameters
 ===================
 
+--defined-tags [complex type]
+
+Defined tags for this resource. Each key is predefined and scoped to a
+namespace. Example: *{“foo-namespace”: {“bar-key”: “value”}}* 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.
+
 --display-name [text]
 
 A user-friendly name. Does not have to be unique, and it’s changeable.
@@ -50,6 +63,19 @@ Example:
 
 Perform update without prompting for confirmation.
 
+--freeform-tags [complex type]
+
+Simple key-value pair that is applied without any predefined name,
+type or scope. Exists for cross-compatibility only. Example: *{“bar-
+key”: “value”}* 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.
+
 --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/fleet-apps-management/fleet-apps-management-catalog/catalog-item/configure.txt

@@ -0,0 +1,218 @@
+"configure"
+***********
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Configures a CatalogItem. Creating new Catalog Item.
+
+
+Usage
+=====
+
+   oci fleet-apps-management fleet-apps-management-catalog catalog-item configure [OPTIONS]
+
+
+Required Parameters
+===================
+
+--bucket-name [text]
+
+The name of the Object Storage bucket that contains the catalog item
+configuration object.
+
+--catalog-item-id [text]
+
+The OCID of the CatalogItem.
+
+--compartment-id, -c [text]
+
+OCID of the Compartment.
+
+--input-variables [complex type]
+
+Array of key value pairs specifying variables or parameters to be used
+when configuring the catalog item. 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.
+
+--storage-namespace [text]
+
+The Oracle Cloud Object Storage namespace where the artifact or
+variables are stored.
+
+
+Optional Parameters
+===================
+
+--catalog-listing-id [text]
+
+The unique identifier of the catalog listing to which configuration
+applies.
+
+--catalog-listing-version-id [text]
+
+The unique identifier for the specific version of the catalog listing.
+
+--defined-tags [complex type]
+
+Defined tags for this resource. Each key is predefined and scoped to a
+namespace. Example: *{“foo-namespace”: {“bar-key”: “value”}}* 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.
+
+--freeform-tags [complex type]
+
+Simple key-value pair that is applied without any predefined name,
+type or scope. Exists for cross-compatibility only. Example: *{“bar-
+key”: “value”}* 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.
+
+--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.
+
+--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.
+
+--object-name [text]
+
+The name of the object file in the specified bucket containing catalog
+item configuration details.
+
+--system-tags [complex type]
+
+System tags for this resource. Each key is predefined and scoped to a
+namespace. Example: *{“orcl-cloud”: {“free-tier-retained”: “true”}}*
+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.
+
+--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-catalog catalog-item configure --generate-param-json-input input-variables > input-variables.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-catalog/catalog-item/create.html#cmdoption-compartment-id
+       export config_source_type=<substitute-value-of-config_source_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-apps-management/fleet-apps-management-catalog/catalog-item/create.html#cmdoption-config-source-type
+       export description=<substitute-value-of-description> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-apps-management/fleet-apps-management-catalog/catalog-item/create.html#cmdoption-description
+       export display_name=<substitute-value-of-display_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-apps-management/fleet-apps-management-catalog/catalog-item/create.html#cmdoption-display-name
+       export package_type=<substitute-value-of-package_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-apps-management/fleet-apps-management-catalog/catalog-item/create.html#cmdoption-package-type
+       export bucket_name=<substitute-value-of-bucket_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-apps-management/fleet-apps-management-catalog/catalog-item/configure.html#cmdoption-bucket-name
+       export storage_namespace=<substitute-value-of-storage_namespace> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-apps-management/fleet-apps-management-catalog/catalog-item/configure.html#cmdoption-storage-namespace
+
+       catalog_item_id=$(oci fleet-apps-management fleet-apps-management-catalog catalog-item create --compartment-id $compartment_id --config-source-type $config_source_type --description $description --display-name $display_name --package-type $package_type --query data.id --raw-output)
+
+       oci fleet-apps-management fleet-apps-management-catalog catalog-item configure --bucket-name $bucket_name --catalog-item-id $catalog_item_id --compartment-id $compartment_id --input-variables file://input-variables.json --storage-namespace $storage_namespace

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet-apps-management-catalog/catalog-item/create-catalog-item-catalog-git-source-config.txt

@@ -119,6 +119,10 @@ 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
 
+--is-item-locked [boolean]
+
+Indicates if the CatalogItem is immutable or not.
+
 --listing-id [text]
 
 The catalog listing Id.

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet-apps-management-catalog/catalog-item/create-catalog-item-catalog-marketplace-source-config.txt

@@ -115,6 +115,10 @@ 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
 
+--is-item-locked [boolean]
+
+Indicates if the CatalogItem is immutable or not.
+
 --listing-id [text]
 
 The catalog listing Id.

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet-apps-management-catalog/catalog-item/create-catalog-item-catalog-par-source-config.txt

@@ -211,6 +211,10 @@ 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
 
+--is-item-locked [boolean]
+
+Indicates if the CatalogItem is immutable or not.
+
 --listing-id [text]
 
 The catalog listing Id.

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet-apps-management-catalog/catalog-item/create-catalog-item-catalog-source-template-config.txt

@@ -124,6 +124,10 @@ 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
 
+--is-item-locked [boolean]
+
+Indicates if the CatalogItem is immutable or not.
+
 --listing-id [text]
 
 The catalog listing Id.

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet-apps-management-catalog/catalog-item/create.txt

@@ -113,6 +113,10 @@ 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
 
+--is-item-locked [boolean]
+
+Indicates if the CatalogItem is immutable or not.
+
 --listing-id [text]
 
 The catalog listing Id.

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet-apps-management-catalog/catalog-item/update.txt

@@ -105,6 +105,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-item-locked [boolean]
+
+Indicates if the CatalogItem is immutable or not.
+
 --max-wait-seconds [integer]
 
 The maximum time to wait for the work request to reach the state

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet-apps-management-catalog/catalog-item-collection/list-catalog-items.txt

@@ -101,6 +101,15 @@ Accepted values are:
 
 The maximum number of items to return.
 
+--package-type [text]
+
+A filter to return only resources that match the given package type.
+The state value is case-insensitive.
+
+Accepted values are:
+
+   CONFIG_FILE, NON_TF_PACKAGE, TF_PACKAGE
+
 --page [text]
 
 A token representing the position at which to start retrieving

oci_cli/help_text_producer/data_files/text/cmdref/fleet-apps-management/fleet-apps-management-catalog/catalog-item-variables-definition/get.txt

@@ -0,0 +1,97 @@
+"get"
+*****
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Gets information about a CatalogItem Variables.
+
+
+Usage
+=====
+
+   oci fleet-apps-management fleet-apps-management-catalog catalog-item-variables-definition get [OPTIONS]
+
+
+Required Parameters
+===================
+
+--catalog-item-id [text]
+
+The OCID of the CatalogItem.
+
+
+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
+
+
+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-catalog/catalog-item/create.html#cmdoption-compartment-id
+       export config_source_type=<substitute-value-of-config_source_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-apps-management/fleet-apps-management-catalog/catalog-item/create.html#cmdoption-config-source-type
+       export description=<substitute-value-of-description> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-apps-management/fleet-apps-management-catalog/catalog-item/create.html#cmdoption-description
+       export display_name=<substitute-value-of-display_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-apps-management/fleet-apps-management-catalog/catalog-item/create.html#cmdoption-display-name
+       export package_type=<substitute-value-of-package_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-apps-management/fleet-apps-management-catalog/catalog-item/create.html#cmdoption-package-type
+
+       catalog_item_id=$(oci fleet-apps-management fleet-apps-management-catalog catalog-item create --compartment-id $compartment_id --config-source-type $config_source_type --description $description --display-name $display_name --package-type $package_type --query data.id --raw-output)
+
+       oci fleet-apps-management fleet-apps-management-catalog catalog-item-variables-definition get --catalog-item-id $catalog_item_id