Dell EMC Synchronize
CertifiedEnterprise EditionSynchronize a Dell EMC PowerStore replication session on demand
Dell EMC Synchronize
Synchronize a Dell EMC PowerStore replication session on demand
Triggers an out-of-band synchronization of a replication session via
POST /api/rest/replication_session/{id}/sync, ahead of its next scheduled RPO. PowerStore
typically accepts this asynchronously (HTTP 202 with a job reference); see wait and waitTimeout.
type: io.kestra.plugin.ee.dellemc.powerstore.replication.SynchronizeExamples
Force an on-demand sync of a replication session before a maintenance window.
id: powerstore_synchronize_replication
namespace: company.team
tasks:
- id: synchronize
type: io.kestra.plugin.ee.dellemc.powerstore.replication.Synchronize
host: "{{ secret('POWERSTORE_HOST') }}"
username: "{{ secret('POWERSTORE_USERNAME') }}"
password: "{{ secret('POWERSTORE_PASSWORD') }}"
sessionId: "{{ inputs.session_id }}"
Properties
host *string
PowerStore management address
Hostname or IP address of the PowerStore appliance management interface, optionally including a
port if non-default (for example: powerstore.example.com or 192.168.1.20: 8443).
The REST API is reached at https://{host}/api/rest.
password *string
PowerStore password
Password for username. Store this value as a Kestra secret and reference it via
{{ secret('POWERSTORE_PASSWORD') }}.
sessionId *string
Replication session ID
ID of the PowerStore replication session to synchronize.
username *string
PowerStore username
Username of a PowerStore local or LDAP account used to authenticate via HTTP Basic Auth.
assets
Assets this task consumes as inputs or produces as outputs, for lineage tracking and the asset graph (Enterprise Edition). A flow declaring this property on a task is rejected in the open-source edition.
io.kestra.core.models.assets.AssetsDeclaration
IGNOREFAILWARNAsset failure behavior
Behavior applied to the task state when a declared asset fails to render, emit, or be persisted (e.g. a lock conflict): FAIL escalates it to FAILED, WARN (default) warns it if it would otherwise succeed, IGNORE leaves the state untouched.
Whether to auto-register assets referenced dynamically at runtime that are not statically declared in inputs or outputs.
The assets consumed as inputs.
io.kestra.core.models.assets.AssetIdentifier
1The assets produced as outputs.
io.kestra.plugin.ee.assets.Dataset
1150{}1150io.kestra.plugin.ee.assets.File
1150{}1150io.kestra.plugin.ee.assets.Table
1150{}1150io.kestra.plugin.ee.assets.VM
1150{}1150io.kestra.core.models.assets.External
1150{}1150io.kestra.core.models.assets.Custom
11501Custom asset type
{}1150skipTlsVerification booleanstring
falseSkip TLS certificate verification
When true, accepts the PowerStore appliance's TLS certificate without validation. Defaults to
false. PowerStore management interfaces are commonly deployed with a self-signed certificate;
set this to true to connect to those without importing the certificate into a trust store.
Intended for lab/non-production use — leave false in production and use a properly signed
certificate instead.
wait booleanstring
trueWait for completion
When the PowerStore array accepts the request asynchronously (HTTP 202 with a job reference),
whether to poll the job until it completes before returning. Defaults to true so downstream
tasks receive a usable result. When false, the task returns immediately with the job ID once
accepted, without waiting for it to finish. Polling blocks the worker thread running this task
for as long as the wait lasts (up to waitTimeout); size the worker pool accordingly if many
job-aware tasks run concurrently, or set this to false and poll separately.
waitTimeout string
PT10MJob wait timeout
Maximum time to wait for an asynchronously accepted job to complete when wait is true.
Defaults to PT10M. Capped at PT30M: values above that are clamped down to PT30M (with a
warning logged) to avoid tying up a worker thread indefinitely. If the timeout elapses before
the job completes, the task returns successfully without confirmed completion — the job ID is
still available in the output so its status can be checked later. Killing the execution while
this task is waiting stops it from polling immediately, but PowerStore's job REST resource has
no cancel/abort endpoint: the array-side operation itself (resize, failover, synchronize,
restore) keeps running to completion on the appliance regardless.
Outputs
pending boolean
Whether the synchronization is still in progress
True when the job did not confirm completion within waitTimeout, or wait was false.
state string
Session state after synchronization
For example: OK. Null if still pending.
