rasulkarimov

@jedcunningham "restricting it artificially" - I agree with your point, I just wanted to follow the established pattern in the "git_sync_container" template. However, using gitSync.env is not ideal because proxy...

> look good, can you fix current tests to validate your changes? Thank you! Fixed tests.

> I'd much rather we move [gitSync.env](https://github.com/apache/airflow/blob/58820a914c9b84c378c9bc1acd4ddbcb4e4a3497/chart/values.schema.json#L7408) to accept [V1EnvVars](https://github.com/apache/airflow/blob/58820a914c9b84c378c9bc1acd4ddbcb4e4a3497/chart/values.schema.json#L8173-L8175) vs restricting it artificially like we are now. > > @rasulkarimov, can you give that approach a shot instead? Can...

> I'd much rather we move [gitSync.env](https://github.com/apache/airflow/blob/58820a914c9b84c378c9bc1acd4ddbcb4e4a3497/chart/values.schema.json#L7408) to accept [V1EnvVars](https://github.com/apache/airflow/blob/58820a914c9b84c378c9bc1acd4ddbcb4e4a3497/chart/values.schema.json#L8173-L8175) vs restricting it artificially like we are now. > > @rasulkarimov, can you give that approach a shot instead? can...