Skip to content

Use base aws classes in amazon provider Operators/Sensors/Triggers #35278

@Taragolis

Description

@Taragolis

Body

Right now some inconsistency exists between different Operators/Sensors/Triggers which are use AwsBaseGeneric hook.
After #34784 and #34884 we could make all of them (except Transfer Operators) use same subset of generic attributes.

It might make more easier to end users use this objects (don't need to think is it region or region_name or is it even support this arguments), as well as make easier extend by new new hook parameters to all this operators in the one go.

General Approach for solve each case:

  • Use AwsBaseOperator for operators, AwsBaseSensor for sensors. In some very specific case e.g. multi inheritance required to use AwsBaseHookMixin (see: AppflowRecordsShortCircuitOperator)
  • Provide additional arguments to AwsBaseWaiterTrigger (if required)
  • Wrap template_fields parameters
  • Attach generic documentation into the service specific page into the Amazon Provider Documentation
  • Validate that all parameters propagated to operator/sensor specific hook

All this steps already done for some of the operators, so it could be use as a reference

Committer

  • I acknowledge that I am a maintainer/committer of the Apache Airflow project.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:providerskind:metaHigh-level information important to the communityprovider:amazonAWS/Amazon - related issues

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions