Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move provider dependencies to inside provider folders #24672

Merged
merged 1 commit into from
Jun 29, 2022

Commits on Jun 29, 2022

  1. Move provider dependencies to inside provider folders

    The ``setup.py`` had ALWAUS contained provider dependencies,
    but this is really a remnant of Airlfow 1.10 where providers
    were not separated out to subfolders of "providers".
    
    This change moves all the provider-specific dependencies
    to provider.yaml where they are kept together with all other
    provider meta-data.
    
    Later, when we move providers out, we can move them to
    provider specific setup.py files (or let provider-specific
    setup.py files read them from provider.yaml) but this is
    not something we want to do it now.
    
    The dependencies.json is now renamed to provider_dependencies.json
    and moved to "airflow" so tha it can be kept as part of the
    sources needed for sdist package to provide extras. Pre-commit still
    generates the file as needed and it contains now both:
    
    * cross-provider-deps information which providers depend on each
      other
    * deps - information what regular dependencies are needed for each
      provider
    
    On top of preparing to splitting providers it has the advantage,
    that there will be no more case where adding a dependency change
    for provider will not run tests for that provider.
    potiuk committed Jun 29, 2022
    Configuration menu
    Copy the full SHA
    6349b5e View commit details
    Browse the repository at this point in the history