oci-cli 3.62.2__py3-none-any.whl → 3.63.0__py3-none-any.whl

oci_cli/help_text_producer/data_files/text/cmdref/marketplace-publisher/{offer/offer/update.txt → listing-revision/update-listing-revision-update-lead-gen-listing-revision-details.txt}

@@ -1,5 +1,5 @@
-"update"
-********
+"update-listing-revision-update-lead-gen-listing-revision-details"
+******************************************************************
 
 * Description
 
@@ -17,31 +17,27 @@
 Description
 ===========
 
-Updates the Offer
+Updates the Listing Revision
 
 
 Usage
 =====
 
-   oci marketplace-publisher offer offer update [OPTIONS]
+   oci marketplace-publisher listing-revision update-listing-revision-update-lead-gen-listing-revision-details [OPTIONS]
 
 
 Required Parameters
 ===================
 
---offer-id [text]
+--listing-revision-id [text]
 
-unique Offer identifier
+listing revision
 
 
 Optional Parameters
 ===================
 
---buyer-compartment-id [text]
-
-OCID of the buyer’s tenancy (root compartment).
-
---buyer-information [complex type]
+--content-language [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
@@ -52,22 +48,6 @@ 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.
 
---custom-fields [complex type]
-
-A list of key value pairs specified by the seller
-
-This option is a JSON list with items of type CustomField.  For
-documentation on CustomField please see our API reference: https://do
-cs.cloud.oracle.com/api/#/en/offer/20220901/datatypes/CustomField.
-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.
-
 --defined-tags [complex type]
 
 Defined tags for this resource. Each key is predefined and scoped to a
@@ -81,18 +61,24 @@ 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]
+--demo-url [text]
 
-Description of the Offer
+Url to demo of the listing
 
 --display-name [text]
 
-Offers Identifier
+The name for the listing revision.
 
---duration [text]
+--download-info [complex type]
 
-Duration the Offer will be active after its start date. An ISO8601
-extended formatted string.
+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.
 
 --force
 
@@ -133,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
 
+--headline [text]
+
+Single line introduction for the listing revision.
+
 --if-match [text]
 
 For optimistic concurrency control. In the PUT or DELETE call for a
@@ -141,226 +131,138 @@ 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.
 
---internal-notes [text]
+--keywords [text]
 
-Internal notes of the Offer
+Keywords associated for the listing revision.
+
+--long-description [text]
+
+A long description for the listing revision.
 
 --max-wait-seconds [integer]
 
 The maximum time to wait for the resource to reach the lifecycle state
 defined by "--wait-for-state". Defaults to 1200 seconds.
 
---pricing [complex type]
+--pricing-plans [text]
 
-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.
+Pricing details for lead gen listing
 
-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.
+--pricing-type [text]
 
---resource-bundles [complex type]
+The pricing model for the listing revision.
 
-A list of Resource Bundles associated with an Offer.
+--products [complex type]
 
-This option is a JSON list with items of type ResourceBundle.  For
-documentation on ResourceBundle please see our API reference: https:/
-/docs.cloud.oracle.com/api/#/en/offer/20220901/datatypes/ResourceBund
-le. 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.
+List of Products subscribed by listing.
+
+This option is a JSON list with items of type ListingProduct.  For
+documentation on ListingProduct please see our API reference: https:/
+/docs.cloud.oracle.com/api/#/en/marketplacepublisher/20241201/datatyp
+es/ListingProduct. 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.
 
---seller-information [complex type]
+--recommended-service-provider-listing-ids [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.
+OCIDs of service listings attached to lead gen listing 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.
 
---time-accept-by [datetime]
-
-The time the Offer must be accepted by the Buyer before the Offer
-becomes invalid. An RFC3339 formatted datetime string
-
-   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::
+--self-paced-training-url [text]
 
-       Format: YYYY-MM-DDTHH:mm:ssTZD
-       Example: 2017-09-15T20:30:00Z
+Url to training resources of the listing
 
-   UTC with minute precision
-   **************************
-   .. code::
+--short-description [text]
 
-       Format: YYYY-MM-DDTHH:mmTZD
-       Example: 2017-09-15T20:30Z
+A short description for the listing revision.
 
+--support-contacts [complex type]
 
-Timezone with microseconds
---------------------------
+Contact information to use to get support from the publisher for the
+listing revision.
 
-   Format: YYYY-MM-DDTHH:mm:ssTZD
-   Example: 2017-09-15T12:30:00.456789-08:00, 2017-09-15T12:30:00.456789-0800
+This option is a JSON list with items of type SupportContact.  For
+documentation on SupportContact please see our API reference: https:/
+/docs.cloud.oracle.com/api/#/en/marketplacepublisher/20241201/datatyp
+es/SupportContact. 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.
 
-   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-date [datetime]
-
-The time the Offer will become active after it has been accepted by
-the Buyer. An RFC3339 formatted datetime string
-
-   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
+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.
 
-   UTC with minute precision
-   **************************
-   .. code::
+--support-links [complex type]
 
-       Format: YYYY-MM-DDTHH:mmTZD
-       Example: 2017-09-15T20:30Z
+Links to support resources for the listing revision.
 
+This option is a JSON list with items of type NamedLink.  For
+documentation on NamedLink please see our API reference: https://docs
+.cloud.oracle.com/api/#/en/marketplacepublisher/20241201/datatypes/Na
+medLink. 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.
 
-Timezone with microseconds
---------------------------
+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.
 
-   Format: YYYY-MM-DDTHH:mm:ssTZD
-   Example: 2017-09-15T12:30:00.456789-08:00, 2017-09-15T12:30:00.456789-0800
+--supportedlanguages [complex type]
 
-   Timezone with milliseconds
-   ***************************
-   .. code::
+Languages supported by the listing revision.
 
-       Format: YYYY-MM-DDTHH:mm:ssTZD
-       Example: 2017-09-15T12:30:00.456-08:00, 2017-09-15T12:30:00.456-0800
+This option is a JSON list with items of type LanguageItem.  For
+documentation on LanguageItem please see our API reference: https://d
+ocs.cloud.oracle.com/api/#/en/marketplacepublisher/20241201/datatypes
+/LanguageItem. 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.
 
-   Timezone without milliseconds
-   *******************************
-   .. code::
+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.
 
-       Format: YYYY-MM-DDTHH:mm:ssTZD
-       Example: 2017-09-15T12:30:00-08:00, 2017-09-15T12:30:00-0800
+--system-requirements [text]
 
-   Timezone with minute precision
-   *******************************
-   .. code::
+System requirements for the listing revision.
 
-       Format: YYYY-MM-DDTHH:mmTZD
-       Example: 2017-09-15T12:30-08:00, 2017-09-15T12:30-0800
+--tagline [text]
 
-   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)
+The tagline for the listing revision.
 
-   .. code::
+--usage-information [text]
 
-       Format: 'YYYY-MM-DD HH:mm' or "YYYY-MM-DD HH:mm"
-       Example: '2017-09-15 17:25'
+Usage information for the listing revision.
 
-   Date Only
-   **********
-   This date will be taken as midnight UTC of that day
+--vanity-url [text]
 
-   .. code::
+Custom link to the listing
 
-       Format: YYYY-MM-DD
-       Example: 2017-09-15
+--version-details [complex type]
 
-   Epoch seconds
-   **************
-   .. code::
+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.
 
-       Example: 1412195400
+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]
 
@@ -410,9 +312,14 @@ 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 display_name=<substitute-value-of-display_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/marketplace-publisher/offer/offer/create.html#cmdoption-display-name
-       export seller_compartment_id=<substitute-value-of-seller_compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/marketplace-publisher/offer/offer/create.html#cmdoption-seller-compartment-id
+       export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/marketplace-publisher/listing/create.html#cmdoption-compartment-id
+       export listing_type=<substitute-value-of-listing_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/marketplace-publisher/listing/create.html#cmdoption-listing-type
+       export name=<substitute-value-of-name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/marketplace-publisher/listing/create.html#cmdoption-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/marketplace-publisher/listing/create.html#cmdoption-package-type
+       export headline=<substitute-value-of-headline> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/marketplace-publisher/listing-revision/create.html#cmdoption-headline
+
+       listing_id=$(oci marketplace-publisher listing create --compartment-id $compartment_id --listing-type $listing_type --name $name --package-type $package_type --query data.id --raw-output)
 
-       offer_id=$(oci marketplace-publisher offer offer create --display-name $display_name --seller-compartment-id $seller_compartment_id --query data.id --raw-output)
+       listing_revision_id=$(oci marketplace-publisher listing-revision create --headline $headline --listing-id $listing_id --listing-type $listing_type --query data.id --raw-output)
 
-       oci marketplace-publisher offer offer update --offer-id $offer_id
+       oci marketplace-publisher listing-revision update-listing-revision-update-lead-gen-listing-revision-details --listing-revision-id $listing_revision_id