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

[DISCUSSION] Orchestrator calling tass modules approach #168

Open
ty-desj opened this issue Oct 17, 2024 · 1 comment
Open

[DISCUSSION] Orchestrator calling tass modules approach #168

ty-desj opened this issue Oct 17, 2024 · 1 comment
Labels
back burner Nice to haves, low priority, or wish list items discussion Issue for discussion and not immediate development

Comments

@ty-desj
Copy link
Collaborator

ty-desj commented Oct 17, 2024

To discuss the implementation of the orchestrator module calling method.

  • Using standard import statements and calling the main function of each module

    • Specific, more efficient and less prone to error
    • Requires refactor to add additional modules to orchestrator
  • Using a dynamic approach, calling the module as if using CMD

    • Allows for easy expansion without requiring a refactor to the orchestrator
    • More prone to human error, incorrect calls could have unexpected results. Would require sanitizing commands beforehand.
@ty-desj ty-desj added back burner Nice to haves, low priority, or wish list items discussion Issue for discussion and not immediate development labels Oct 17, 2024
@ty-desj
Copy link
Collaborator Author

ty-desj commented Oct 17, 2024

@DominicParent as we discussed, a few of the options that we can look at for calling other modules, for discussion

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
back burner Nice to haves, low priority, or wish list items discussion Issue for discussion and not immediate development
Projects
None yet
Development

No branches or pull requests

1 participant