[Feature Request]: Add Support for Sharing lifecycleEnvironments Directly in Project Configuration Files

[dsanderbi]

What would you like to happen?

Currently, Apache Hop lacks the capability to share lifecycleEnvironments along with the project configuration files in a way that ensures consistency across all developers.

When a new environment is added or modified for a project, the changes are made in the hop-config.json file. This file is user-specific and not shared through the project repository, leading to the following issue:

Manual Updates: Developers need to manually update their local hop-config.json files to reflect changes made by others, which can be cumbersome and error-prone.

I'd like to request the addition of a feature that allows lifecycleEnvironments to be linked directly to the project configuration files (project-config.json or a similar project-specific file). This would involve:

• Integration: Storing lifecycleEnvironments in a project-specific configuration file that is version-controlled and included in the project repository.
• Automatic Synchronization: Ensuring that changes to environments are automatically reflected for all developers working on the project, without requiring manual updates to individual hop-config.json files.

See also: https://chat.project-hop.org/hop/pl/f936cqzr5b8fj8fzccxpzod3no

Issue Priority

Priority: 2

Issue Component

Component: Hop Config

[gmitter-ef]

Any plans on this feature? We would really like to be able to store environments and their json files not in hop-config.json, but project-config.json!

[bamaer]

work in progress if I'm not mistaken.

[gmitter-ef]

Great to hear that! In the course of some other ticket?

[hansva]

.take-issue