oci-cli 3.71.4__py3-none-any.whl → 3.72.1__py3-none-any.whl

oci_cli/help_text_producer/data_files/text/cmdref/budgets/cost-ad/cost-anomaly-monitor/create.txt

@@ -0,0 +1,192 @@
+"create"
+********
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Creates a new costAnomaly Monitor.
+
+
+Usage
+=====
+
+   oci budgets cost-ad cost-anomaly-monitor create [OPTIONS]
+
+
+Required Parameters
+===================
+
+--compartment-id, -c [text]
+
+The OCID of the compartment.
+
+--name [text]
+
+The name of the cost anomaly monitor. Avoid entering confidential
+information.
+
+--target-resource-filter [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
+===================
+
+--cost-alert-subscription-map [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.
+
+--defined-tags [complex type]
+
+Defined tags for this resource. Each key is predefined and scoped to a
+namespace. For more information, see Resource Tags.
+
+Example:
+
+   {"Operations": {"CostCenter": "42"}}
+
+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]
+
+The description of the cost anomaly monitor.
+
+--freeform-tags [complex type]
+
+Free-form tags for this resource. Each tag is a simple key-value pair
+with no predefined name, type, or namespace. For more information, see
+Resource Tags.
+
+Example:
+
+   {"Department": "Finance"}
+
+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
+
+--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.
+
+--wait-for-state [text]
+
+This operation creates, modifies or deletes a resource that has a
+defined lifecycle state. Specify this option to perform the action and
+then wait until the resource reaches a given lifecycle 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:
+
+   ACTIVE, DELETED, INACTIVE
+
+--wait-interval-seconds [integer]
+
+Check every "--wait-interval-seconds" to see whether the resource has
+reached the lifecycle 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", "--enable-dual-stack", "--enable-propagation", "--
+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 budgets cost-ad cost-anomaly-monitor create --generate-param-json-input target-resource-filter > target-resource-filter.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/budgets/cost-ad/cost-anomaly-monitor/create.html#cmdoption-compartment-id
+       export name=<substitute-value-of-name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/budgets/cost-ad/cost-anomaly-monitor/create.html#cmdoption-name
+
+       oci budgets cost-ad cost-anomaly-monitor create --compartment-id $compartment_id --name $name --target-resource-filter file://target-resource-filter.json

oci_cli/help_text_producer/data_files/text/cmdref/{devops/pull-request/reopen-pull-request-comment.txt → budgets/cost-ad/cost-anomaly-monitor/delete.txt}

@@ -1,5 +1,5 @@
-"reopen-pull-request-comment"
-*****************************
+"delete"
+********
 
 * Description
 
@@ -17,30 +17,30 @@
 Description
 ===========
 
-Reopen a PullRequest Comment
+Deletes a specified CostAnomalyMonitor resource.
 
 
 Usage
 =====
 
-   oci devops pull-request reopen-pull-request-comment [OPTIONS]
+   oci budgets cost-ad cost-anomaly-monitor delete [OPTIONS]
 
 
 Required Parameters
 ===================
 
---comment-id [text]
+--cost-anomaly-monitor-id [text]
 
-unique PullRequest Comment identifier
-
---pull-request-id [text]
-
-unique PullRequest identifier
+The unique costAnomalyMonitor OCID.
 
 
 Optional Parameters
 ===================
 
+--force
+
+Perform deletion without prompting for confirmation.
+
 --from-json [text]
 
 Provide input to this command as a JSON document from a file using the
@@ -71,6 +71,32 @@ 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 resource to reach the lifecycle state
+defined by "--wait-for-state". Defaults to 1200 seconds.
+
+--wait-for-state [text]
+
+This operation creates, modifies or deletes a resource that has a
+defined lifecycle state. Specify this option to perform the action and
+then wait until the resource reaches a given lifecycle 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:
+
+   ACTIVE, DELETED, INACTIVE
+
+--wait-interval-seconds [integer]
+
+Check every "--wait-interval-seconds" to see whether the resource has
+reached the lifecycle state defined by "--wait-for-state". Defaults to
+30 seconds.
+
 
 Global Parameters
 =================
@@ -94,7 +120,7 @@ Example using required parameter
 Copy and paste the following example into a JSON file, replacing the
 example parameters with your own.
 
-       oci devops project create --generate-param-json-input notification-config > notification-config.json
+       oci budgets cost-ad cost-anomaly-monitor create --generate-param-json-input target-resource-filter > target-resource-filter.json
 
 Copy the following CLI commands into a file named example.sh. Run the
 command by typing “bash example.sh” and replacing the example
@@ -104,17 +130,9 @@ 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/devops/project/create.html#cmdoption-compartment-id
-       export name=<substitute-value-of-name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/devops/project/create.html#cmdoption-name
-       export repository_type=<substitute-value-of-repository_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/devops/repository/create.html#cmdoption-repository-type
-       export display_name=<substitute-value-of-display_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/devops/pull-request/create.html#cmdoption-display-name
-       export source_branch=<substitute-value-of-source_branch> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/devops/pull-request/create.html#cmdoption-source-branch
-       export comment_id=<substitute-value-of-comment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/devops/pull-request/reopen-pull-request-comment.html#cmdoption-comment-id
-
-       project_id=$(oci devops project create --compartment-id $compartment_id --name $name --notification-config file://notification-config.json --query data.id --raw-output)
-
-       repository_id=$(oci devops repository create --name $name --project-id $project_id --repository-type $repository_type --query data.id --raw-output)
+       export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/budgets/cost-ad/cost-anomaly-monitor/create.html#cmdoption-compartment-id
+       export name=<substitute-value-of-name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/budgets/cost-ad/cost-anomaly-monitor/create.html#cmdoption-name
 
-       pull_request_id=$(oci devops pull-request create --display-name $display_name --repository-id $repository_id --source-branch $source_branch --query data.id --raw-output)
+       cost_anomaly_monitor_id=$(oci budgets cost-ad cost-anomaly-monitor create --compartment-id $compartment_id --name $name --target-resource-filter file://target-resource-filter.json --query data.id --raw-output)
 
-       oci devops pull-request reopen-pull-request-comment --comment-id $comment_id --pull-request-id $pull_request_id
+       oci budgets cost-ad cost-anomaly-monitor delete --cost-anomaly-monitor-id $cost_anomaly_monitor_id

oci_cli/help_text_producer/data_files/text/cmdref/{devops/pull-request/resolve-pull-request-comment.txt → budgets/cost-ad/cost-anomaly-monitor/disable.txt}

@@ -1,5 +1,5 @@
-"resolve-pull-request-comment"
-******************************
+"disable"
+*********
 
 * Description
 
@@ -17,25 +17,22 @@
 Description
 ===========
 
-Resolve a PullRequest Comment
+Disables the cost anomaly monitor. This stops cost anomaly detection
+for targeted resource(s).
 
 
 Usage
 =====
 
-   oci devops pull-request resolve-pull-request-comment [OPTIONS]
+   oci budgets cost-ad cost-anomaly-monitor disable [OPTIONS]
 
 
 Required Parameters
 ===================
 
---comment-id [text]
+--cost-anomaly-monitor-id [text]
 
-unique PullRequest Comment identifier
-
---pull-request-id [text]
-
-unique PullRequest identifier
+The unique costAnomalyMonitor OCID.
 
 
 Optional Parameters
@@ -71,6 +68,32 @@ 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 resource to reach the lifecycle state
+defined by "--wait-for-state". Defaults to 1200 seconds.
+
+--wait-for-state [text]
+
+This operation creates, modifies or deletes a resource that has a
+defined lifecycle state. Specify this option to perform the action and
+then wait until the resource reaches a given lifecycle 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:
+
+   ACTIVE, DELETED, INACTIVE
+
+--wait-interval-seconds [integer]
+
+Check every "--wait-interval-seconds" to see whether the resource has
+reached the lifecycle state defined by "--wait-for-state". Defaults to
+30 seconds.
+
 
 Global Parameters
 =================
@@ -94,7 +117,7 @@ Example using required parameter
 Copy and paste the following example into a JSON file, replacing the
 example parameters with your own.
 
-       oci devops project create --generate-param-json-input notification-config > notification-config.json
+       oci budgets cost-ad cost-anomaly-monitor create --generate-param-json-input target-resource-filter > target-resource-filter.json
 
 Copy the following CLI commands into a file named example.sh. Run the
 command by typing “bash example.sh” and replacing the example
@@ -104,17 +127,9 @@ 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/devops/project/create.html#cmdoption-compartment-id
-       export name=<substitute-value-of-name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/devops/project/create.html#cmdoption-name
-       export repository_type=<substitute-value-of-repository_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/devops/repository/create.html#cmdoption-repository-type
-       export display_name=<substitute-value-of-display_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/devops/pull-request/create.html#cmdoption-display-name
-       export source_branch=<substitute-value-of-source_branch> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/devops/pull-request/create.html#cmdoption-source-branch
-       export comment_id=<substitute-value-of-comment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/devops/pull-request/resolve-pull-request-comment.html#cmdoption-comment-id
-
-       project_id=$(oci devops project create --compartment-id $compartment_id --name $name --notification-config file://notification-config.json --query data.id --raw-output)
-
-       repository_id=$(oci devops repository create --name $name --project-id $project_id --repository-type $repository_type --query data.id --raw-output)
+       export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/budgets/cost-ad/cost-anomaly-monitor/create.html#cmdoption-compartment-id
+       export name=<substitute-value-of-name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/budgets/cost-ad/cost-anomaly-monitor/create.html#cmdoption-name
 
-       pull_request_id=$(oci devops pull-request create --display-name $display_name --repository-id $repository_id --source-branch $source_branch --query data.id --raw-output)
+       cost_anomaly_monitor_id=$(oci budgets cost-ad cost-anomaly-monitor create --compartment-id $compartment_id --name $name --target-resource-filter file://target-resource-filter.json --query data.id --raw-output)
 
-       oci devops pull-request resolve-pull-request-comment --comment-id $comment_id --pull-request-id $pull_request_id
+       oci budgets cost-ad cost-anomaly-monitor disable --cost-anomaly-monitor-id $cost_anomaly_monitor_id

oci_cli/help_text_producer/data_files/text/cmdref/budgets/cost-ad/cost-anomaly-monitor/enable.txt

@@ -0,0 +1,135 @@
+"enable"
+********
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Enables the cost anomaly monitor. This (re)starts the cost anomaly
+detection for targeted resource(s).
+
+
+Usage
+=====
+
+   oci budgets cost-ad cost-anomaly-monitor enable [OPTIONS]
+
+
+Required Parameters
+===================
+
+--cost-anomaly-monitor-id [text]
+
+The unique costAnomalyMonitor OCID.
+
+
+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.
+
+--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.
+
+--wait-for-state [text]
+
+This operation creates, modifies or deletes a resource that has a
+defined lifecycle state. Specify this option to perform the action and
+then wait until the resource reaches a given lifecycle 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:
+
+   ACTIVE, DELETED, INACTIVE
+
+--wait-interval-seconds [integer]
+
+Check every "--wait-interval-seconds" to see whether the resource has
+reached the lifecycle 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", "--enable-dual-stack", "--enable-propagation", "--
+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 budgets cost-ad cost-anomaly-monitor create --generate-param-json-input target-resource-filter > target-resource-filter.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/budgets/cost-ad/cost-anomaly-monitor/create.html#cmdoption-compartment-id
+       export name=<substitute-value-of-name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/budgets/cost-ad/cost-anomaly-monitor/create.html#cmdoption-name
+
+       cost_anomaly_monitor_id=$(oci budgets cost-ad cost-anomaly-monitor create --compartment-id $compartment_id --name $name --target-resource-filter file://target-resource-filter.json --query data.id --raw-output)
+
+       oci budgets cost-ad cost-anomaly-monitor enable --cost-anomaly-monitor-id $cost_anomaly_monitor_id

oci_cli/help_text_producer/data_files/text/cmdref/budgets/cost-ad/cost-anomaly-monitor/get.txt

@@ -0,0 +1,100 @@
+"get"
+*****
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Gets a CostAnomalyMonitor by the identifier.
+
+
+Usage
+=====
+
+   oci budgets cost-ad cost-anomaly-monitor get [OPTIONS]
+
+
+Required Parameters
+===================
+
+--cost-anomaly-monitor-id [text]
+
+The unique costAnomalyMonitor OCID.
+
+
+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", "--enable-dual-stack", "--enable-propagation", "--
+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 budgets cost-ad cost-anomaly-monitor create --generate-param-json-input target-resource-filter > target-resource-filter.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/budgets/cost-ad/cost-anomaly-monitor/create.html#cmdoption-compartment-id
+       export name=<substitute-value-of-name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/budgets/cost-ad/cost-anomaly-monitor/create.html#cmdoption-name
+
+       cost_anomaly_monitor_id=$(oci budgets cost-ad cost-anomaly-monitor create --compartment-id $compartment_id --name $name --target-resource-filter file://target-resource-filter.json --query data.id --raw-output)
+
+       oci budgets cost-ad cost-anomaly-monitor get --cost-anomaly-monitor-id $cost_anomaly_monitor_id