You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A clear and concise description of what the bug is. Plain-text snippets preferred but screenshots welcome.
The App Gen DAG should fail if there is an error in the entrypoint.sh i.e. cannot clone the provided git repo
Right now, it is not failing, it still shows up as successful but no credentials are printed in the logs
If I change the entrypoint.sh that creates the application package to return exit code 1 when there is an error, then the credentials are printed in the logs
I think there are 2 ways to approach this and I already tried the first option:
More securely pass the credentials so that they are not printed when the DAG is printed on error. I tried passing as arguments, env vars, using the env parameter, using the from_env parameter, started looking into using kubernetes secrets
Change something so that the failed DAG is not printed on fail
I will also need to make modifications to the entrypoint.sh so that it exists with exit code nonzero when there is an error
What did you expect?
A clear and concise description of what you expect to happen
The App Gen DAG should fail if there is an error in the entrypoint.sh i.e. cannot clone the provided git repo
And no credentials should be printed to the logs
Reproducible steps
How would we reproduce this bug? Please walk us through it step by step. Plain-text snippets preferred but screenshots welcome.
Register the App Gen DAG from unity-sps/airflow/dags/appgen_dag.py
Trigger the DAG with a nonexistent repo
The DAG will say it is successful but the logs say that it failed to execute all of the entrypoint.sh
What is your environment?
Include any computer hardware, operating system, framework, browser, time-of-day or other contextual information related to your issue
I am working in my SPS deployment instance
The text was updated successfully, but these errors were encountered:
Checked for duplicates
Describe the bug
I think there are 2 ways to approach this and I already tried the first option:
I will also need to make modifications to the entrypoint.sh so that it exists with exit code nonzero when there is an error
What did you expect?
Reproducible steps
What is your environment?
I am working in my SPS deployment instance
The text was updated successfully, but these errors were encountered: