"ingest-sql-plan-lines"
***********************

* Description

* Usage

* Optional Parameters

* Global Parameters

* Example using required parameter


Description
===========

The SqlPlanLines endpoint takes in a JSON payload, persists it in
Operation Insights ingest pipeline. Either databaseId or id must be
specified.


Usage
=====

   oci opsi database-insights ingest-sql-plan-lines [OPTIONS]


Optional Parameters
===================

--compartment-id, -c [text]

The OCID of the compartment.

--database-id [text]

Optional OCID of the associated DBaaS entity.

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

--id [text]

OCID of the database insight resource.

--if-match [text]

Used for optimistic concurrency control. In the update or delete call
for a resource, set the *if-match* parameter to the value of the etag
from a previous get, create, or update response for that resource.
The resource will be updated or deleted only if the etag you provide
matches the resource’s current etag value.

--items [complex type]

List of SQL Plan Line Entries.

This option is a JSON list with items of type SqlPlanLine.  For
documentation on SqlPlanLine please see our API reference: https://do
cs.cloud.oracle.com/api/#/en/operationsinsights/20200630/datatypes/Sq
lPlanLine. 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.


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.

       oci opsi database-insights ingest-sql-plan-lines
