Skip to content

Conversation

@Taragolis
Copy link
Contributor

@Taragolis Taragolis commented Aug 20, 2023

During #33557 found that SnowflakeToSlackOperator is a deprecated version of SqlToSlackOperator

In additional I would like to remove S3ToSnowflakeOperator which is deprecated version of more generic CopyFromExternalStageToSnowflakeOperator

Maybe it is also a good idea to remove SnowflakeOperator, which is also deprecated

ToDo:

  • Update documentation if required
  • Add breaking changes

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

@Taragolis Taragolis requested a review from eladkal August 20, 2023 17:24
@boring-cyborg boring-cyborg bot added area:providers area:system-tests provider:snowflake Issues related to Snowflake provider labels Aug 20, 2023
@Taragolis Taragolis force-pushed the snowflake-remove-remove-deprecated-stuff branch from 386fd57 to f8363ba Compare August 20, 2023 17:25
@Taragolis Taragolis force-pushed the snowflake-remove-remove-deprecated-stuff branch from f8363ba to 992a091 Compare August 20, 2023 18:35
@Taragolis Taragolis force-pushed the snowflake-remove-remove-deprecated-stuff branch from 992a091 to f5b498b Compare August 20, 2023 19:16
@Taragolis Taragolis marked this pull request as ready for review August 20, 2023 19:16
Copy link
Member

@potiuk potiuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@potiuk potiuk merged commit 86423b4 into apache:main Aug 21, 2023
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we should somehow find a way to indicate that this capability is still available via other provider (in automated manner)

My thought here is that users who need this capability might not look at Slack docs. I think it can be very nice if we can indicate in the provider about all the capabilities that can be used with this service regardless if their code base is part of this provider or not (simply mention it existed and reference to the right package but in an automated way)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants