-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
🔌 Plugin: Parodos #178
Comments
The plugins so far live here: https://github.com/parodos-dev/backstage-parodos , they are subject of migration to janus-idp for further development. |
We track this work on our end here: https://issues.redhat.com/browse/FLPATH-203 |
Are there any docs on how to implement the parodos workflow engine? |
Do you mean how to implement workflows? if so you can find some info and examples here |
We have a task which can post to tibco. That is why we have a dependency on tibco client. At the moment we support one workflow engine (easy-flows) but we have an epic to write an abstraction and support more engines. |
Thanks for sharing, is there currently a list of engines in scope? |
No list at this time |
This issue has been closed due to the fact that the Janus community is being sunset. For future plugin issues, please use https://github.com/backstage/community-plugins/issues For future showcase issues, please use https://issues.redhat.com/browse/RHIDP For more information on the sunset, see: https://janus-idp.io/blog/2024/07/05/future-of-janus-community |
Goal
This epic aims to develop a new Backstage plugin in the Janus repo. This plugin should allow Backstage users to access guided flows driven by the Parodos workflow engine.
Acceptance criteria
Requirements
Issues in Epic
Notes
Parodos workflow engine - community repo: https://github.com/redhat-developer/parodos
The text was updated successfully, but these errors were encountered: