This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 29f1adf7ca Update README_RELEASE_PROVIDER_PACKAGES.md (#34246)
29f1adf7ca is described below
commit 29f1adf7cab107e5fdb64aa59533085aacb203d1
Author: Elad Kalif <[email protected]>
AuthorDate: Sat Sep 9 21:43:08 2023 +0300
Update README_RELEASE_PROVIDER_PACKAGES.md (#34246)
---
dev/README_RELEASE_PROVIDER_PACKAGES.md | 12 +-----------
1 file changed, 1 insertion(+), 11 deletions(-)
diff --git a/dev/README_RELEASE_PROVIDER_PACKAGES.md
b/dev/README_RELEASE_PROVIDER_PACKAGES.md
index 4629126046..852b7f147b 100644
--- a/dev/README_RELEASE_PROVIDER_PACKAGES.md
+++ b/dev/README_RELEASE_PROVIDER_PACKAGES.md
@@ -351,14 +351,6 @@ breeze build-docs --clean-build --package-filter
apache-airflow-providers \
--package-filter 'apache-airflow-providers-*'
```
-You can also use shorthand names as arguments instead of using the full names
-for airflow providers. Example:
-
-```shell script
-cd "${AIRFLOW_REPO_ROOT}"
-breeze build-docs cncf.kubernetes sftp --clean-build
-```
-
Usually when we release packages we also build documentation for the
"documentation-only" packages. This
means that unless we release just few selected packages or if we need to
deliberately skip some packages
we should release documentation for all provider packages and the above
command is the one to use.
@@ -379,17 +371,15 @@ for airflow providers. Example:
```shell script
cd "${AIRFLOW_REPO_ROOT}"
-breeze build-docs package1 package2 --clean-build
+breeze build-docs providers-index cncf.kubernetes sftp --clean-build
```
-
If you have providers as list of provider ids because you just released them,
you can build them with
```shell script
./dev/provider_packages/build_provider_documentation.sh amazon apache.beam
google ....
```
-
- Now you can preview the documentation.
```shell script
