Gallardot commented on issue #17252: URL: https://github.com/apache/dolphinscheduler/issues/17252#issuecomment-2976186293
> > Yes, I hope that I don’t need to frequently switch online operations during debugging, and I can release it to production after debugging is completed. > > In this case, I think we should create a namespace to isolate the environment, instead of transforming existing workflows and tasks. Because in addition to these, others, such as data source center, resource center, queue, tenant, workgroup, permissions and so on, need to be isolated. And then we should create a way to publish from one namespace to another. @SbloodyS @det101 Resource isolation represents a complex project that likely exceeds the intrinsic capabilities of DolphinScheduler itself. As a workflow scheduling system, it may not be the optimal component for this responsibility, or resource isolation might not inherently fall within the core purview of a scheduler. DolphinScheduler should remain focused on its primary target scenarios. Regarding the optimization for debugging scenarios mentioned in the Issue: Disregarding resource isolation considerations, would providing a synchronized replication and overwrite functionality for workflows suffice? Consider these practical deployment scenarios: Create a production (prod) project containing production workflows. Create a development (dev) project containing development workflows. Upon successful validation of a development workflow, enable one-click synchronization to overwrite its corresponding workflow in the production project. Alternatively: Within the same project, create both a development (dev) workflow and a production (prod) workflow. Upon successful validation of the development workflow, enable one-click synchronization to overwrite the production workflow within the same project. (Note: The terms "production (prod)" and "development (dev)" here serve solely as environmental labels for identification purposes and do not imply resource isolation.) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
