serverless-operations / serverless-operations/serverless-step-functions
Share/Split step functions to orchestrate across multiple monorepo services
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 220
- PR merge metrics
- No merged PRs in 30d
Description
This is a Question
Description
I'm looking for some guidance on how to write step functions that orchestrate multiple services that are segregated by their own serverless.yml file.
Do I have one service (serverless.yml) directory with all the step functions and they do some kind of import of the other serverless files?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the plugin's handling of serverless.yml files and the Serverless Framework setup for Step Functions. Determine whether orchestration across separately defined services is supported or would require a new design; the issue is resolved only when the supported configuration or implementation scope is clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100