You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add feture of "not-ready" provider. (apache#36391)
This PR adds possibility of marking the provider as "not ready" in the
provider.yaml (by setting optional field as "not-ready" to `true".
Setting provider as "not-ready", removes it by default from all the
release management commands - preparing documentation files preparing
provider packages, publishing docs.
You can include such providers via `--include-not-ready-providers`
flag (or setting INCLUDE_NOT_READY_PROVIDERS environment variable to
true).
This flag is set to True in our CI, so that we can make sure the
providers in-progress are also being tested and verified, but when
release manager prepares packages, those providers are not prepared.
That will help in early stage of a lifecycle of a provider when we
already want to iterate and test it continuously, but - for example
the API of such provider is not yet stable or when we are in progress
of moving functionality for such provider from core.
This PR also marks `fab` providers as "not-ready" as it is still
early days and we want to exclude it for now from any kind of release
process.
Copy file name to clipboardexpand all lines: airflow/provider.yaml.schema.json
+4
Original file line number
Diff line number
Diff line change
@@ -29,6 +29,10 @@
29
29
"description": "If set to true, the provider is also removed and will be soon removed from the code",
30
30
"type:": "boolean"
31
31
},
32
+
"not-ready": {
33
+
"description": "If set to true, the provider is not included by default in release commands - for example when provider release or documentation is being prepared (not-ready providers are enabled in CI by default)",
34
+
"type:": "boolean"
35
+
},
32
36
"dependencies": {
33
37
"description": "Dependencies that should be added to the provider",
0 commit comments