6863jh opened a new issue, #72318:
URL: https://github.com/apache/airflow/issues/72318
### Under which category would you file this issue?
Airflow Core
### Apache Airflow version
3.3.1
### What happened and how to reproduce it?
Clicking "Test" in the UI for a connection whose type doesn't use
`host`/`port`
(e.g. `snowflake`) always fails with errors like:
The private_key_file path points to an empty or invalid file.
even when the connection is verified working via
`airflow connections test <conn_id>` on the CLI, and the underlying
credentials/file are valid.
### What you think should happen instead?
Test Connection should succeed using the already-saved connection's
credentials, same as the CLI `airflow connections test` command does.
### Operating System
rocky9.4
### Deployment
Docker-Compose
### Apache Airflow Provider(s)
_No response_
### Versions of Apache Airflow Providers
_No response_
### Official Helm Chart version
Not Applicable
### Kubernetes Version
_No response_
### Helm Chart configuration
_No response_
### Docker Image customizations
Not using the official Airflow Docker image. Custom container running
scheduler, api-server, dag-processor, triggerer, and an Edge Executor
worker as separate daemonized processes inside a single container
(MySQL as the metadata DB, running under Rosetta emulation on Apple
Silicon). No modifications to Airflow's own source/behavior beyond
standard pip-installed apache-airflow-core==3.3.1.
### Anything else?
_No response_
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
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]
