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

Additional properties should be allowed in provider schema #13440

Commits on Jan 3, 2021

  1. Additional properties should be allowed in provider schema

    The additional properties should be allowed in provider schema,
    otherwise future version of providers will not be compatible with
    older versions of Airflow.
    
    Specifying 'additionalProperties' as allowed we are opening up to
    adding more properties to provider.yaml.
    
    This change fixes this is for now by removing extra fields
    added since the Airlow 2.0.0 schema and verifying that the 2.0.0
    schema correctly validates such modified dictionary.
    
    In the future we might deprecate 2.0.0 and add >=2.0.1 limitation
    to the provider packages in which case we will be able to remove
    this modification of the provider_info dict.
    
    Also added additional test for provider packages whether they
    install on Airflow 2.0.0. This tests might remain even after the
    deprecation of 2.0.0 - we can just move it to 2.0.1. However this
    will give us much bigger confidence that the providers will
    continue work even for older versions of Airflow 2.0.
    
    We might have to modify that test and only include the providers
    that are backwards-compatible, in case we have some providers
    that depend on future Airflow versions. For now we assume
    all providers should be installable from master on 2.0.0.
    potiuk committed Jan 3, 2021
    Configuration menu
    Copy the full SHA
    007bab7 View commit details
    Browse the repository at this point in the history