Skip to content

Conversation

@Pigius
Copy link
Contributor

@Pigius Pigius commented Jul 11, 2021

Big picture behind

Currently, there aren't many examples of using the serverless approach with Ruby for AWS. Ruby is a great and mature language with a great community and lots of gems.

General message

There are not many examples of Step Functions, and some of the existing ones do not use the Step Functions plugin, but have a ready-made schema that you can copy.

Luckily we also now have Workflow Studio for AWS Step Functions, so it's easier to design state machines.

Diagrams could be found here:

step-functions-diagram

step-functions-detailed

Extra points:

  • There is an issue with using sls variables with this plugin, there are already issues for that.
  • Used the Ruby.27 runtime, as for the Ruby2.5 will be End of Support at the end of August.

@pgrzesik
Copy link
Contributor

Thanks @Pigius 🙌 As discussed, it's temporarily paused until serverless-operations/serverless-step-functions#451 is merged and new version of the plugin is released, due to incompatibility with new variable resolver.

@Pigius
Copy link
Contributor Author

Pigius commented Aug 5, 2021

@pgrzesik the package for the step function was updated to the newest version. Everything works seamlessly. Ready to be checked by you 🚀

Copy link
Contributor

@pgrzesik pgrzesik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks great, thank you @Pigius 🙇 I have only one question about seemingly unrelated change that landed in this PR and we should be good to go 💯

README.md Outdated
- [Contributing](#contributing)
- [Adding example code](#adding-example-code)
- [Adding a community example](#adding-a-community-example)
- [Getting Started](#getting-started)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm guessing this should not be a part of this PR, right? :D

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pgrzesik fixed. Not sure what it changed, I've run npm run docs and this happened :/ But fixed anyway :)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting, I'll look into it 💯

@Pigius Pigius requested a review from pgrzesik August 9, 2021 08:13
Copy link
Contributor

@pgrzesik pgrzesik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for awesome, as always, contribution @Pigius 🙇

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants