airflow: Snowflake provider: The `private_key_content` field is no longer a multi-line text input in Connections

Apache Airflow Provider(s)

snowflake

Versions of Apache Airflow Providers

apache-airflow-providers-snowflake==6.0.0

Apache Airflow version

2.10.5

Operating System

Debian GNU/Linux 12 (bookworm)

Deployment

Docker-Compose

Deployment details

No response

What happened

The “Private key (text)” field for Snowflake connections should be a multi-line text input box, but is a password field instead: Image

This seems to be a regression introduced in this commit. Pasting a private key in PEM format fails because the line breaks do not paste well in the box as is.

This used to work well in version 5.7.0 of the provider.

What you think should happen instead

No response

How to reproduce

Install Apache Airflow with apache-airflow[snowflake]==2.10.5, start the webserver and go to Connections. Open the snowflake_default connection to see the incorrect input type for private key content.

Anything else

This prevents setting up a Snowflake connection with private key authentication.

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 16 (11 by maintainers)

Most upvoted comments

Base64 sounds logical, but wouldn’t that create a breaking change for users upgrading from an older version of the operator?
They might need to resubmit their keys in the connections to prevent pipeline failures.

That said, versions newer than 5.7 are already breaking pipelines anyway.

Can we maybe extend the BS3PasswordFieldWidget and have our own widget that will behave the same but NOT replace \n - I think that would be the cleanest way to handle it.