Skip to content
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

Closed
6 tasks
serenamarie125 opened this issue Mar 17, 2023 · 9 comments
Closed
6 tasks

🔌 Plugin: Parodos #178

serenamarie125 opened this issue Mar 17, 2023 · 9 comments

Comments

@serenamarie125
Copy link
Contributor

serenamarie125 commented Mar 17, 2023

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

  • Users should be able to xxx (need to flesh out the first version of ACs)
  • [ ]

Requirements

  • Plugin
  • Test plan
  • Installation documentation
  • End user documentation

Issues in Epic

  • tbd

Notes

Parodos workflow engine - community repo: https://github.com/redhat-developer/parodos

@mareklibra
Copy link
Contributor

The plugins so far live here: https://github.com/parodos-dev/backstage-parodos , they are subject of migration to janus-idp for further development.

@pkliczewski
Copy link

We track this work on our end here: https://issues.redhat.com/browse/FLPATH-203

@regicsolutions
Copy link

Are there any docs on how to implement the parodos workflow engine?

@pkliczewski
Copy link

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

@regicsolutions
Copy link

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

This helps, regarding the example is there a dependency on tibco?

Is there a list of supported workflow engines?

@pkliczewski
Copy link

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.

@regicsolutions
Copy link

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?

@pkliczewski
Copy link

Thanks for sharing, is there currently a list of engines in scope?

No list at this time

@rhdh-bot
Copy link
Collaborator

rhdh-bot commented Sep 3, 2024

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
https://issues.redhat.com/browse/RHIDP-3690
https://issues.redhat.com/browse/RHIDP-1018

@rhdh-bot rhdh-bot closed this as completed Sep 3, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants