Skip to content
This repository has been archived by the owner on May 27, 2021. It is now read-only.

3.0dev Master Tracking Issue #186

Closed
7 of 10 tasks
LindsayHill opened this issue Dec 5, 2018 · 6 comments
Closed
7 of 10 tasks

3.0dev Master Tracking Issue #186

LindsayHill opened this issue Dec 5, 2018 · 6 comments

Comments

@LindsayHill
Copy link
Contributor

LindsayHill commented Dec 5, 2018

This issue will track more specific issues identified during pre-3.0 release testing.

High Priority - ship blockers

Medium Priority

Low Priority

@Kami
Copy link
Member

Kami commented Dec 6, 2018

StackStorm/st2web#626 fixes #180.

I only added support for Orquesta since @enykeev removed support for action chain here - be4e6cd.

If we still / also want to support action chain we need to add it back in those two places.

@LindsayHill
Copy link
Contributor Author

I'm fine with not supporting Action Chain - we have not supported it before, so it's OK to not support it in 3.0. If the code is there and we can later get it working in 3.1, that's OK. But is not needed for 3.0.

@Kami
Copy link
Member

Kami commented Dec 6, 2018

Yeah, @enykeev confirmed it was never supported so I updated the issue to reflect that and only added a link to edit for Orquesta workflows.

@m4dcoder
Copy link
Contributor

m4dcoder commented Dec 6, 2018

Then the Action Chain entry should be remove from the drop down box in the st2flow editor.

@LindsayHill
Copy link
Contributor Author

@m4dcoder

since @enykeev removed support for action chain here - be4e6cd.

@bigmstone
Copy link
Contributor

Closing in favor of 3.0 milestone.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants