dmainou commented on issue #5237: URL: https://github.com/apache/hop/issues/5237#issuecomment-3071340272
Hi @mattcasters yes, something like that. Great if you can list the target project and target environments to export in one go. The scenario I have is that I am developing in my local, then passing on to others to move between environments. these 'others' have no interest in learning things they will simply execute scripts I supply (this is true for a CI/CD pipeline as well). At present I'm creating, one bash scripts for every project and every environment. The scripts simply use hop run to create things in a consistent way. However this is a one way route and requires effort to ensure their validity over time. e.g. If you add a 2nd conf file to an environment you'll then need to remember to add it to the Environment creation script. Then you need to delete your environment , run the script and observe the environment created. It's a lot of conscious work. This is also hard to sustain if more than one dev is working on the same project. It would be great to provide teams with the ability to hit the ground running by allowing a simple way to create or update a project and it's environments in the exact same way as everyone else shortly after pulling the repository. Thank you! -- 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]
