A Flow That Says Whether It Can Call Anything Before You Run It
A Serverless Workflow flow and its schedules. role_arn is optional in the API, so a flow without one is created, reads correctly in the console and fails at the first task that touches another service - at execution time. The module refuses that, and turns schedules on, because the API default is off and a disabled schedule shows its cron expression anyway.
Verification
Static-verifiedPassed: validated and lint-clean (provider-schema-validated for AWS/Azure/GCP; Terraform-language lint elsewhere).
Conformance
- Static validation (fmt · validate · tflint)
- No applicable security policies for this provider
- Plan tests (mocked: validation rules · outputs)
Provenance
- SHA-256 checksum
- Signature (pending)
Functional
- Live test pending (no cloud run yet)
Last verified 2026-09-15 · how we verify
Use it from the registry
terraform · opentofumodule "workflows" {
source = "www.iac-bazaar.com/iac-bazaar/alicloud-workflows/alicloud"
version = "1.0.0"
}Needs a registry token from /account/tokens. The module itself is free; the account is what identifies you. Full setup: registry docs.
Inputs & outputs
Create a free account to read this module's contract
The declared contract - every input name, type, default and description, plus every output - is shown to signed-in accounts, not to anonymous visitors.
A free account sees the contract of every module in the catalogue. There is no subscription and nothing to buy - the modules are free to download, and they run under Vizier.
Documentation
alicloud-workflows
Serverless workflow orchestration on Alibaba Cloud Serverless Workflow. Works with Terraform and OpenTofu
(>= 1.6), alicloud provider >= 1.0, < 2.0.
A flow without a role cannot call anything. The API takes role_arn as optional, so the flow is created, reads correctly in the console, and fails at the first task that touches another service. can_call_other_services is an output and the module refuses an empty role unless you say the definition is pure control flow.
A schedule created disabled fires nothing, and the API default is disabled. Schedules here are on, and disabled_schedule_names lists any that are not.
The definition is the product and Terraform checks nothing in it. A misspelled state name is a clean plan today and a runtime failure on the first execution, which is why the module takes a string you keep in a reviewed file.
A schedule payload that is not valid JSON fails at the first execution, so it is checked here instead.
Verification
Static validation runs tofu fmt, init, validate, tflint and checkov.
This module has not yet had a live test, so it is published as statically
validated with its live test pending and does not carry the live-tested mark.
Usage code & full reference need an account
The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.
- Usage
Related modules
gcp-workflows
A Cloud Workflows workflow that runs as a dedicated least-privilege service account instead of the broad Compute Engine default, with inline YAML, deletion protection, and call logging.
azure-logic-app
An Azure Logic App (Consumption) workflow with a built-in Recurrence trigger - serverless pay-per-execution automation with a system-assigned managed identity and inbound IP allowlists.
aws-step-functions
A Step Functions state machine (STANDARD or EXPRESS) with a least-privilege execution role, a managed CloudWatch log group, X-Ray tracing, and encryption at rest - working out of the box from a single name.