update

Description

Updates the Scheduled Action resource.

Usage

oci db scheduled-action update [OPTIONS]

Required Parameters

--scheduled-action-id [text]

The Scheduled Action OCID.

Optional Parameters

--action-members [complex type]

The list of action members in a scheduled action.

This option is a JSON list with items of type ActionMember. For documentation on ActionMember please see our API reference: https://docs.cloud.oracle.com/api/#/en/database/20160918/datatypes/ActionMember. 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.

--action-params [complex type]

Map<ParamName, ParamValue> where a key value pair describes the specific action parameter. Example: {“count”: “3”} 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

Perform update without prompting for confirmation.

--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/Content/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.

--scheduling-window-id [text]

The OCID of the Scheduling Window.

--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:

AVAILABLE, CREATING, DELETED, DELETING, FAILED, NEEDS_ATTENTION, UPDATING
--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.

Example using required parameter

Copy and paste the following example into a JSON file, replacing the example parameters with your own.

    oci db scheduling-window create --generate-param-json-input window-preference > window-preference.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 cadence=<substitute-value-of-cadence> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/scheduling-policy/create.html#cmdoption-cadence
    export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/scheduling-policy/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/db/scheduling-policy/create.html#cmdoption-display-name
    export resource_id=<substitute-value-of-resource_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/scheduling-plan/create.html#cmdoption-resource-id
    export service_type=<substitute-value-of-service_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/scheduling-plan/create.html#cmdoption-service-type
    export scheduling_policy_id=<substitute-value-of-scheduling_policy_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/scheduling-window/create.html#cmdoption-scheduling-policy-id
    export action_type=<substitute-value-of-action_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/db/scheduled-action/create.html#cmdoption-action-type

    scheduling_policy_id=$(oci db scheduling-policy create --cadence $cadence --compartment-id $compartment_id --display-name $display_name --query data.id --raw-output)

    scheduling_plan_id=$(oci db scheduling-plan create --compartment-id $compartment_id --resource-id $resource_id --scheduling-policy-id $scheduling_policy_id --service-type $service_type --query data.id --raw-output)

    scheduling_window_id=$(oci db scheduling-window create --scheduling-policy-id $scheduling_policy_id --window-preference file://window-preference.json --query data.id --raw-output)

    scheduled_action_id=$(oci db scheduled-action create --action-type $action_type --compartment-id $compartment_id --scheduling-plan-id $scheduling_plan_id --scheduling-window-id $scheduling_window_id --query data.id --raw-output)

    oci db scheduled-action update --scheduled-action-id $scheduled_action_id