shivanandullagaddi opened a new issue, #6502:
URL: https://github.com/apache/hop/issues/6502
Hi Team,
I am running Hop pipelines and workflows through Hop Server REST API from
AWS Lambda.
Pipelines are working correctly using:
1. /hop/registerPipeline
2. /hop/prepareExec
3. /hop/startPipeline
**During registerPipeline, I inject runtime variables like:**
${USERNAME}
${PASSWORD}
${TOKEN}
${SRC_SF_URL}
${APP_SF_URL}
${CONNECTIONID}
These resolve correctly inside all pipeline transforms.
**🔹 My Workflow Scenario**
Now I am triggering a workflow (.hwf) instead of a single pipeline.
Workflow structure:
- Workflow → multiple pipelines → Salesforce transforms
Inside those pipelines I use:
- ${USERNAME}
- ${PASSWORD}
- ${TOKEN}
But:
1. I am NOT using parameters
2. I am NOT passing anything in the Parameters tab
3. I want to pass everything dynamically at runtime from Lambda
**### 🔹 Problem / Confusion**
For pipelines:
- register → prepare → start
But for workflows I only see:
- /hop/registerWorkflow
- /hop/startWorkflow
I cannot find any:
- prepareWorkflowExec
endpoint in documentation.
**### 🔹 My Questions**
1. Is there intentionally no prepare endpoint for workflows?
2. If yes, are variables passed during registerWorkflow automatically
available to:
- workflow
- all child pipelines
- all transforms
4. Will ${VARIABLE_NAME} resolve correctly inside pipelines triggered by the
workflow without parameters?
5. Is the correct execution flow simply:
- registerWorkflow → startWorkflow
6. Is this the recommended production approach for runtime variable
injection?
### **🔹 My current approach**
During registerWorkflow, I inject:
<variables>
USERNAME
PASSWORD
TOKEN
SRC_SF_URL
APP_SF_URL
CONNECTIONID
</variables>
Then I call:
/hop/startWorkflow
Just want confirmation this is the correct and supported design.
Thanks in advance 🙌
--
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]
