[Bug]: Duplication of Run Configurations

[dave-csc]

Apache Hop version?

2.9.0

Java version?

openjdk 21.0.2 2024-01-16

Operating system

Linux

What happened?

If you create a new Pipeline or Workflow Run Configuration via the "Duplicate" command in Hop GUI (Metadata perspective), the associated JSON is created in the same folder the original one resides.

When creating a new Run Configuration (RC) from scratch, instead, the file is saved in the metadata folder related to the active project. This should be a better choice even for duplicates, since you probably don't want a new RC to be available to various projects (all projects, if the original RC belongs to the "default" project).

A workaround consists in moving (manually via OS) the JSON file associated to the new RC to the designed folder. The new RC would be still available on inherited projects, too.

Issue Priority

Priority: 3

Issue Component

Component: Hop Gui

[bamaer]

can you confirm this only happens with projects that have a parent project and the original workflow/parent run configuration that is duplicated is inherited from the parent project?

[dave-csc]

I post a couple of tests to reproduce:

TEST 1 (post above)

1. Choose a project that has a parent project, and "default" as its ancestor (i.e. direct or indirect parent)
2. Duplicate the "local" RC (since it's saved on the "default" project, it is available on all its descendants)
3. Choose another project, the new RC is available

TEST 2

1. Create a new project that has no parent project (not even "default", you have to leave the field blank manually), name it "test"
2. You will be asked to create a new environment and a new "local" RC, answer Yes
3. Create a second project, that has the "test" project as parent, name it "test2" and select it
4. You will find the inherited "local" RC among the (Pipeline or Workflow) Run Configurations, duplicate it
5. Move to the "test" project again
6. You will find the duplicated RC (in "test2") among the Run Configurations in the "test" project

After the workaround (moving manually the associated JSON files to the correct folder under ${PROJECT_HOME}/metadata), the RC is available on the project with ${PROJECT_HOME} and its descendants, but not on parents and siblings (as it is with newly created RCs).

Hope this helps