kaxil commented on PR #71713: URL: https://github.com/apache/airflow/pull/71713#issuecomment-5942548300
Why doesn't a persistent bundle volume cover this? `GitDagBundle` already reuses a pinned version from disk (`_is_pruned_worktree`), and the new `shallow` option adds a second clone path that sets up `origin` itself, outside the bare-clone retry and credential handling main has added since. Every future auth fix would need to be made in both places, and the option becomes a permanent bundle kwarg. Is there an issue or a user hitting this on Kubernetes? Converting to draft until there is. -- 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]
