Skip to main content

Oracle Cloud node

An Oracle Cloud node lets you interact with Oracle Cloud Infrastructure (OCI) services from a flow. Use it to retrieve or manage resources and pass the output to later nodes.

Oracle Cloud nodes are available to customers enrolled in Early Access.

Before you begin​

Oracle Cloud nodes reuse an OCI Asset already connected to DoiT. Create an Oracle Cloud connection, then select it when you configure the node.

The IAM policy used for billing ingestion does not grant access to OCI Core resources. Add the CloudFlow IAM policy described in the Oracle Cloud connection guide before testing an action.

Configure an action​

When adding an action node, select Oracle Cloud, then search or browse the available services.

  • Parameters: Select an accessible compartment and subscribed region, or enter their identifiers directly, then configure the parameters required by the operation.
  • Connection: Select an Oracle Cloud connection that has access to the target compartment.
  • Test: Test read-only nodes before publishing the flow. Review the warning below before testing an operation that changes resources. See Test nodes.

Oracle Cloud nodes follow paginated responses that use the opc-next-page response header.

Require approval​

Oracle Cloud operations classified as destructive, including DeleteVolume and DeletePublicIp, require approval. Configure the approval to expire in hours, with an expiry of no more than 24 hours. InstanceAction changes the state of a compute instance, so we recommend requiring approval for it as well. See Configure approvals.

Immediately before deletion, CloudFlow retrieves the resource again and uses its ETag for a conditional request:

  • A block volume must be AVAILABLE and have no active attachment in any accessible compartment in the selected region.
  • A public IP must be AVAILABLE, RESERVED, and unassigned.

These checks reduce race conditions but don't determine whether a volume or address is still needed for backups, DNS, allowlists, disaster recovery, infrastructure as code, or another business process.

Caution

Testing an Oracle Cloud node runs the operation and doesn't display its configured approval. Testing START or SOFTSTOP changes the real resource. Testing a DeleteVolume or DeletePublicIp node can delete every resource resolved from its upstream candidate list.

Limitations​

During Early Access:

  • Connections can only reuse an active OCI Asset. You can't create dedicated Oracle credentials in CloudFlow.
  • CloudFlow generates its Oracle Cloud service and operation catalog from the pinned official OCI SDK. Service API versions follow the SDK metadata.
  • Structured JSON control-plane operations are supported. Streaming, binary, multipart, WebSocket, and object-content transfer operations aren't available.
  • InstanceAction supports START and graceful stop (SOFTSTOP) only.
  • Region and compartment selectors appear only for operations that require those values. Home-region and global operations resolve their endpoints from the connected OCI Asset.
  • An action node can evaluate up to 100 requests and sends no more than five OCI requests concurrently.
  • An operation fails if pagination exceeds 100 pages.
  • Permission checks are read-only probes. Delete and power-action permissions are verified only when the operation runs.
  • An operation permission check requires literal values for its required scope fields. Referenced values are resolved at runtime.

OCI IAM and resource-level policies can only be fully verified when an operation runs.

See also​

Last updated on