Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document a best practice to have modules dedicated to contain only code for orchestration flows #9692

Closed
LuqiPan opened this issue Jul 12, 2024 · 0 comments · Fixed by #9726
Assignees
Labels
enhancement New feature or request

Comments

@LuqiPan
Copy link
Contributor

LuqiPan commented Jul 12, 2024

What is the Problem Being Solved?

Without E support in asyncFlow, it's a best practice to have modules dedicated to contain only code for orchestration flows, we (OpCo) should document this behavior so developer can follow this convention.

Description of the Design

Security Considerations

Scaling Considerations

Test Plan

Upgrade Considerations

@LuqiPan LuqiPan added the enhancement New feature or request label Jul 12, 2024
@turadg turadg self-assigned this Jul 15, 2024
@turadg turadg mentioned this issue Jul 17, 2024
@mergify mergify bot closed this as completed in #9726 Jul 18, 2024
@mergify mergify bot closed this as completed in c3009d4 Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants