Feature Request: Support Passing API Token or Session ID in Hightouch Airflow Operator #28
Description
Description:
Currently, the Hightouch Airflow operator requires an Airflow connection for authentication, which means storing API keys in Airflow (even if encrypted). It would be useful to allow passing an API token or session ID directly, enabling dynamic authentication without relying on Airflow connections.
Proposed Solution:
Add support for passing an api_token or session_id directly to the operator.
Allow users to fetch credentials dynamically from secret managers like Vault instead of storing them in Airflow.
Use Case:
- Users who manage secrets externally and want to avoid storing credentials in Airflow.
- More flexibility in authentication methods.
Would this be feasible to add? Happy to discuss further!