Airflow provides the XCom mechanism to communicate small amounts of data between tasks. In order to move data from one task to a Studio Flow or Job Execution, we could enable templating for the Operator parameters. For the SASJobExecutionOperator, the "parameters" parameter could be templated and for the SASStudioFlowOperator, the "env_vars" parameter could be templated.
This would enable sas-airflow-provider users to use templated values for those two parameters, meaning that data could be passed from one task into a sas-airflow-provider task, then into the Studio Flow or Job Execution via the "env_vars" or "parameters" parameter.
Airflow provides the XCom mechanism to communicate small amounts of data between tasks. In order to move data from one task to a Studio Flow or Job Execution, we could enable templating for the Operator parameters. For the SASJobExecutionOperator, the "parameters" parameter could be templated and for the SASStudioFlowOperator, the "env_vars" parameter could be templated.
This would enable sas-airflow-provider users to use templated values for those two parameters, meaning that data could be passed from one task into a sas-airflow-provider task, then into the Studio Flow or Job Execution via the "env_vars" or "parameters" parameter.