You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned in this PR by @thiagomanel, the solution addressed makes SAPS responsible for searching the script in two files, one of which is intended only for the test scripts (nop and endtoend).
For a better solution, it was thought to use only 1 configuration file that starts a script table in the Catalog and after that new scripts will be added from an endpoint on the Dispatcher backend and thus not needing SAPS to search for files, in addition to leaving it free to receive new scripts without being dropped and raised again.
In addition, a CLI to use the new route would be feasible to maintain as a new resource in the project (which will be used by some scripts, for example, systemtest script)
The text was updated successfully, but these errors were encountered:
As mentioned in this PR by @thiagomanel, the solution addressed makes SAPS responsible for searching the script in two files, one of which is intended only for the test scripts (nop and endtoend).
For a better solution, it was thought to use only 1 configuration file that starts a script table in the Catalog and after that new scripts will be added from an endpoint on the Dispatcher backend and thus not needing SAPS to search for files, in addition to leaving it free to receive new scripts without being dropped and raised again.
In addition, a CLI to use the new route would be feasible to maintain as a new resource in the project (which will be used by some scripts, for example, systemtest script)
The text was updated successfully, but these errors were encountered: