pankajkoti commented on issue #31551: URL: https://github.com/apache/airflow/issues/31551#issuecomment-1564233713
> > yes, along with being a bug, I will consider it as a breaking change as users like us would not have set host but set the connection extras cluster_identidifer: <cluster_identifier> together with iam: true, which would be needed for such configuration and it breaks existing running DAGs. > > I don't agree, IMO this is just a new broken feature, setting `iam` to false or removing it is sufficient to deactivate the feature and avoid the bug. If the new feature is broken and does not have an effect outside the scope of the feature, I believe it's fine. But it is affecting existing running DAGs too because the earlier setup connection has `iam:true`. Here existing configuration is becoming invalid and is producing unexpected results due to the change in the PR. Curious to understand why having to alter the connection/configuration by having to set `iam: false` is not a breaking change by itself. Also, setting `iam:false` may disable this feature but has wider implications. I would like to continue using IAM authentication to connect to the cluster https://airflow.apache.org/docs/apache-airflow-providers-amazon/stable/connections/redshift.html#examples -- 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]
