This is an automated email from the ASF dual-hosted git repository.
hansva pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/hop.git
The following commit(s) were added to refs/heads/main by this push:
new 5633443ea2 fix wrong references to hop-config , fixes #6453 (#6459)
5633443ea2 is described below
commit 5633443ea293049340be2d1938f5aa93ada682dc
Author: Hans Van Akelyen <[email protected]>
AuthorDate: Mon Jan 26 13:07:55 2026 +0100
fix wrong references to hop-config , fixes #6453 (#6459)
---
docker/resources/load-and-execute.sh | 2 +-
docs/hop-tech-manual/modules/ROOT/pages/docker-container.adoc | 2 +-
.../modules/ROOT/pages/pipeline/beam/getting-started-with-beam.adoc | 2 +-
.../pipeline-run-configurations/beam-flink-pipeline-engine.adoc | 2 +-
.../pipeline-run-configurations/beam-spark-pipeline-engine.adoc | 2 +-
docs/hop-user-manual/modules/ROOT/pages/variables.adoc | 4 ++--
6 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/docker/resources/load-and-execute.sh
b/docker/resources/load-and-execute.sh
index 8def03b7fb..30f3be66a8 100755
--- a/docker/resources/load-and-execute.sh
+++ b/docker/resources/load-and-execute.sh
@@ -204,7 +204,7 @@ if [ -n "${HOP_CONFIG_OPTIONS}" ]; then
# We have a hop-config to run with the given options
#
echo "Configuring Hop with : ${HOP_CONFIG_OPTIONS}"
- "${DEPLOYMENT_PATH}"/hop-config.sh \
+ "${DEPLOYMENT_PATH}"/hop-conf.sh \
"{HOP_CONFIG_OPTIONS}" \
2>&1 | tee ${HOP_LOG_PATH}
fi
diff --git a/docs/hop-tech-manual/modules/ROOT/pages/docker-container.adoc
b/docs/hop-tech-manual/modules/ROOT/pages/docker-container.adoc
index 84ca471f71..3d8eb98b4d 100644
--- a/docs/hop-tech-manual/modules/ROOT/pages/docker-container.adoc
+++ b/docs/hop-tech-manual/modules/ROOT/pages/docker-container.adoc
@@ -119,7 +119,7 @@ You can specify the properties as a comma separated list,
e.g. `PROP1=xxx,PROP2=
|```HOP_CONFIG_OPTIONS```
|
-|If you specify a value for this variable, they will be used to execute
`hop-config.sh` right before execution of the short- or long-lived container.
+|If you specify a value for this variable, they will be used to execute
`hop-conf.sh` right before execution of the short- or long-lived container.
You can use it for example to configure values for keys, plugins, and so on.
|===
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/beam/getting-started-with-beam.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/beam/getting-started-with-beam.adoc
index 6ace00a5c5..467b85ff41 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/beam/getting-started-with-beam.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/beam/getting-started-with-beam.adoc
@@ -243,7 +243,7 @@ Apache Hop allows you to create a fat jar in the Hop GUI
with the `Tools/Generat
[source]
----
-sh hop-config.sh -fj /path/to/fat.jar
+sh hop-conf.sh -fj /path/to/fat.jar
----
The path to this fat jar can then be referenced in the various Beam runtime
configurations.
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/pipeline-run-configurations/beam-flink-pipeline-engine.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/pipeline-run-configurations/beam-flink-pipeline-engine.adoc
index 2c820e0a28..4ceffda981 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/pipeline-run-configurations/beam-flink-pipeline-engine.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/pipeline-run-configurations/beam-flink-pipeline-engine.adoc
@@ -119,7 +119,7 @@ This can be generated in the Hop GUI under the tools menu
or using command:
[source,bash]
----
-sh hop-config.sh -fj /path/to/fat.jar
+sh hop-conf.sh -fj /path/to/fat.jar
----
**Important** : project configurations, environments and these things are not
valid in the context of the Flink runtime.
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/pipeline-run-configurations/beam-spark-pipeline-engine.adoc
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/pipeline-run-configurations/beam-spark-pipeline-engine.adoc
index e881a4d8cc..d296bd56b9 100644
---
a/docs/hop-user-manual/modules/ROOT/pages/pipeline/pipeline-run-configurations/beam-spark-pipeline-engine.adoc
+++
b/docs/hop-user-manual/modules/ROOT/pages/pipeline/pipeline-run-configurations/beam-spark-pipeline-engine.adoc
@@ -107,7 +107,7 @@ This can be generated in the Hop GUI under the tools menu
or using command:
[source,bash]
----
-sh hop-config.sh -fj /path/to/fat.jar
+sh hop-conf.sh -fj /path/to/fat.jar
----
**Important** : project configurations, environments and these things are not
valid in the context of the Spark runtime.
diff --git a/docs/hop-user-manual/modules/ROOT/pages/variables.adoc
b/docs/hop-user-manual/modules/ROOT/pages/variables.adoc
index 7acf3aaa15..0cf3ce66aa 100644
--- a/docs/hop-user-manual/modules/ROOT/pages/variables.adoc
+++ b/docs/hop-user-manual/modules/ROOT/pages/variables.adoc
@@ -205,7 +205,7 @@ CAUTION: even though you _can_ manually change the
`hop-config.json` or any of t
You can also use the hop-config command line tool to define system properties:
[source,bash]
-sh hop-config.sh -s MY_SYSTEM_PROPERTY=SomeValue
+sh hop-conf.sh -s MY_SYSTEM_PROPERTY=SomeValue
@@ -218,7 +218,7 @@ This helps you configure folders and other things which are
environment specific
You can set those in the
xref:projects/projects-environments.adoc#_create_an_environment[environment
settings dialog] or using the command line:
[source,bash]
-sh hop-config.sh -e MyEnvironment -em -ev VARIABLE1=value1
+sh hop-conf.sh -e MyEnvironment -em -ev VARIABLE1=value1
=== Run Configurations
