Dear Hoppists, Project and metadata inheritance, default project, standard samples project, options, ... as discussed in this very thread: all in PR588 <https://github.com/apache/incubator-hop/pull/588> I wrote some documentation <https://github.com/apache/incubator-hop/blob/e283fa33eeafef308687c40201d69422b8658430/plugins/misc/projects/src/main/doc/projects.adoc> on the subject.
Note: this is not the end of the progress on this topic, just the beginning. Feedback is welcome. A review of the PR wouldn't hurt. Cheers, Matt On Thu, Jan 28, 2021 at 1:23 PM Matt Casters <[email protected]> wrote: > To reflect what I just said on the chat, these are all great options and > we should make the behavior configurable really. > We have a very flexible and pluggable configuration system. We should use > it. > > Sure, we can have a "default" project and a "samples" project and then we > can allow Hop to be configured to force usage of a project, to not force > it, to pick the default without specification and so on. > Later on when we have implemented HOP-2269 > <https://issues.apache.org/jira/browse/HOP-2269> we can have metadata > inherited from a project like "default" and so on. > > What I would strongly advocate for in all these scenarios is to properly > explain to the end-user what's going on in the logging. > > - "Selecting a project is configured to be mandatory when executing a > pipeline. Please specify one with option -j" > - "No project was specified. Hop is using project 'default' to run this > pipeline". > etc. > > Cheers, > Matt > > On Thu, Jan 28, 2021 at 1:05 PM Jortilles <[email protected]> wrote: > >> >> Hello Hoppers >> >> After reading for a while. In my opinion, I would go for option 1. >> Although simplifying it as much as possible. Just giving it a name and a >> location. It's not that much. And creating a default environment and run >> configuration. >> With my experience. If you allow option 2 or 3, most users will end up >> doing dirty things that they will regret later on. >> Another question that arises to me is how we will transfer projects from >> development to production. if the configuration of the available projects >> is in $ HOP/config/hop-config.json. Will there be an export - import >> projec? >> > > >
