At the moment, I need to create a separate package for each script I want to use. These packages are then referenced in a Launch Package action. While this approach works, it has a major limitation: it does not allow returning exit codes from the scripts. This makes it difficult to handle success/failure logic or chain actions based on script outcomes.
Problem:
Scripts cannot be reused efficiently across different workflows without duplicating them into multiple packages.
Lack of exit code support prevents proper error handling and conditional logic.
Proposed Solution:
Introduce a script repository (repro) feature that allows storing and managing reusable scripts in a centralized location.
Key capabilities should include:
Ability to reference scripts from the repository in multiple actions without creating separate packages.
Support for returning exit codes from scripts to enable robust error handling and conditional execution.
Optional versioning for scripts to maintain consistency across environments.
Benefits:
Reduces duplication and maintenance overhead.
Improves workflow flexibility and reliability.
Enables better automation by leveraging exit codes for decision-making.
| Product | Application Workspace |