manipatnam opened a new issue, #57984:
URL: https://github.com/apache/airflow/issues/57984

   ### Apache Airflow Provider(s)
   
   snowflake
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-snowflake==6.6.0
   
   ### Apache Airflow version
   
   2.11.0
   
   ### Operating System
   
   debian
   
   ### Deployment
   
   Astronomer
   
   ### Deployment details
   
   _No response_
   
   ### What happened
   
   When creating/editing a Snowflake connection, adding raw JSON to **Extras** 
like:
   
   ```json
   {"account": "1234"}
   ```
   
   gets replaced on save by:
   
   ```json
   {"insecure_mode": false}
   ```
   
   If you instead type “Account” in the dedicated Snowflake field and save, the 
value reappears in **Extras** on reopen. But entering `account` directly in 
**Extras** is lost/overwritten.
   
   ### What you think should happen instead
   
   - Saving a connection should **not** delete/overwrite user-supplied keys 
entered directly in **Extras** if they’re valid for the connection type.
       
   
   ### How to reproduce
   
   
   1. Go to **Admin → Connections → +** (or edit an existing connection).
       
   2. Set **Conn Type** = **Snowflake**.
       
   3. In **Extras** (raw JSON), paste:
       
       ```json
       {"account": "1234"}
       ```
       
   4. Click **Save**.
       
   5. Reopen the connection.
       
   
   **Result:** **Extras** now shows:
   
   ```json
   {"insecure_mode": false}
   ```
   
   Your `account` key is gone.
   
   ### 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]

Reply via email to