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
Currently, the Web Tools web application uses a very close image to the sonataflow-devmode-image. We should unify them into one and use the very same on the operator and web tools side.
Goals
Make the SonataFlow Operator Web Tools image to share the same Quarkus Devmode image
Disable the zip upload feature on the Operator side to avoid a security breach
Motivation
We should unify these images since the operator and web tools share the same requirements. One image serving both tools would increase our maintainability and resource use.
Description
The serverless-logic-web-tools-swf-dev-mode-image has a backdoor that the web tools use to update the project files via a ZIP structure. To avoid security breaches, this backdoor must be disabled by default and only enabled by the Web Tools when refreshing the application.
After this work, we can safely remove one of the packages to save build and maintenance resources.
Testing
The exact use case offered today by the web tools and the operator Operator continues to work.
Deploy one workflow with Web Tools, check the running status, and if it creates a workflow instance without any occurrences
Repeat the process with the OperatorOperatortcome must be the same
Risks
Fail to turn off the ZIP backdoor on the Operator deployment.
The text was updated successfully, but these errors were encountered:
Summary
Currently, the Web Tools web application uses a very close image to the sonataflow-devmode-image. We should unify them into one and use the very same on the operator and web tools side.
Goals
Motivation
We should unify these images since the operator and web tools share the same requirements. One image serving both tools would increase our maintainability and resource use.
Description
The
serverless-logic-web-tools-swf-dev-mode-image
has a backdoor that the web tools use to update the project files via a ZIP structure. To avoid security breaches, this backdoor must be disabled by default and only enabled by the Web Tools when refreshing the application.After this work, we can safely remove one of the packages to save build and maintenance resources.
Testing
The exact use case offered today by the web tools and the operator Operator continues to work.
Risks
Fail to turn off the ZIP backdoor on the Operator deployment.
The text was updated successfully, but these errors were encountered: