Sync v2-7-stable with v2-7-test to release 2.7.2 #34775
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We should only tag :latest image when default image is used because this step always tags `apache/airflow:X.Y.Z` (defaulti Python) to become the `apache/airflow:latest`. This step was previously run for all Python versions which could have two effects: * if non-default image completed before the default such tagging would fail as the `apache/airflow:X.Y.Z` was not ready yet to be used as target of `apache/airflow:latesti` tag * if non-default image completed later, it would be no-op because the `apache/airflow:latest` already pointed to `apache/airflow:X.Y.Z` (cherry picked from commit 51d8b10)
* better command line support with better auto-complete * allows to run back-referance generation for individual provider packages * better typing including using Pathlib everywhere * handling of redirection between providers - when an operator is moved from one provider to the other - instead of generating invalid "stable" link we generate back reference for all versions of the provider. (cherry picked from commit 14faf19)
This is a better fix for add-back-references breeze command, as the previous fix had a bug and processed more than just providers when providers --gen-type was selected. See #33149. This version fixes it in a much more consistent way: * you have to specify what you want to work on as option * you can select few of the provider via auto-complete * you can also select apache-airflow and helm-chart * you can mix and match them if you need All the scripts and references where `--gen-type` was used previously have been updated and documentation was changed to reflect it (cherry picked from commit 8c28454)
(cherry picked from commit 50abdce)
(cherry picked from commit e434ae8)
(cherry picked from commit 94f70d8)
(cherry picked from commit 2dbb963)
Co-authored-by: Tzu-ping Chung <[email protected]> (cherry picked from commit 85acbb4)
(cherry picked from commit 0e00564)
(cherry picked from commit ba0bab0)
(cherry picked from commit 8aa2229)
(cherry picked from commit 94c8291)
Currently, the candidates are ordered by the PR number but ordering by the closed date is better and will help avoid some conflicts (cherry picked from commit 90628e4)
(cherry picked from commit cfa5477)
(cherry picked from commit a44f261)
(cherry picked from commit a1d4a20)
) (cherry picked from commit 4e545c8)
(cherry picked from commit 1e81ed1)
(cherry picked from commit 660386b)
ephraimbuddy
requested review from
jedcunningham,
dstandish,
kaxil,
pierrejeambrun,
potiuk,
ashb,
eladkal and
o-nikolas
as code owners
…4293) Some of the recent sqlalchemy changes are not working with minimum version of sqlalchemy of ours - for example `where` syntax does not allow moe than one clause and we are already passing more in _do_delete_old_records (added in #33527). This syntax however was added in SQL Alchemy 1.4.28 and our minimum version was 1.4.27. This change bumps the minimum SQLAlchemy version to 1.4.28 but it also adds a special test job that only runs on Postgres that downgrades the SQLAlchemy to the minimum supported version (retrieved from setup.cfg). This way, we will be able to detect such incompatible changes at the PR time. This is a new flag `--downgrade-sqlalchemy` on test command that works similar to earlier `--upgrade-boto`. We also enable the `--upgrade-boto` and `--downgrade-sqlalchemy` flags to be used for `breeze shell` command - thanks to that we can easily test both flags with `breeze shell` command. (cherry picked from commit efbead9)
* Refactor: Simplify code in breeze --------- Co-authored-by: Tzu-ping Chung <[email protected]> (cherry picked from commit 7c950a8)
It's been quite some time since we bumped min versions for docker and docker-compose for Breeze and there are already a few cases where it held us back from more efficiently using some newer docker or docker-compose features (for example in #33547). Also docker-compose v1 is sufficiently old an unmaintained, that it's about time to get rid of it and ask the users to migrate to docker-compose v2. The new min versions propose: * Docker: 23.0.0 released 2023-02-01 (6 months ago) * Docker Compose 2.14.0 release 2022-12-15 (8 months ago) Docker v1 is not supported any more and the users are directed to migrate to v2 to continue using Breeze. (cherry picked from commit 73a3733)
In case docker is run in rootless mode, the host UID is mapped to root user automatically and host user id is mapped to 100999 (unknown) so changing ownership for created files in rootless mode is problematic as it makes the generated files inaccessible (cherry picked from commit 0631af8)
* Avoid WSL2 ones when finding a context for Breeze * fixup! Avoid WSL2 ones when finding a context for Breeze --------- Co-authored-by: Tzu-ping Chung <[email protected]> (cherry picked from commit 2e764fb)
(cherry picked from commit 1928498)
(cherry picked from commit 6618c5f)
ephraimbuddy
force-pushed
the
v2-7-test
branch
from
dd2252d to
2bef523
Compare
eladkal
reviewed
Oct 5, 2023
| - Add missing audit logs for Flask actions add, edit and delete (#34090) | ||
| - Hide Irrelevant Dag Processor from Cluster Activity Page (#33611) | ||
| - Remove infinite animation for pinwheel, spin for 1.5s (#34020) | ||
| - Restore rendering of provider configuration with ``version_added`` (#34011) |
There was a problem hiding this comment.
this is internal change is it not?
There was a problem hiding this comment.
It's a bug: #34005
* Fix autodetect_docker_context for list of dict case * Handle the case of dict (cherry picked from commit 5c2dc53)
ephraimbuddy
force-pushed
the
v2-7-test
branch
from
2bef523 to
7d09fcb
Compare
eladkal
approved these changes
Oct 6, 2023
hussein-awala
approved these changes
Oct 6, 2023
ephraimbuddy
force-pushed
the
v2-7-test
branch
2 times, most recently
from
3207ade to
24ab656
Compare
pierrejeambrun
approved these changes
Oct 7, 2023
(cherry picked from commit 1f3525f)
ephraimbuddy
force-pushed
the
v2-7-test
branch
from
24ab656 to
c8b25cb
Compare
|
The failure in "pull request target" can be ignored. All the remaining steps in "pull request target" workflow are generally ignored when PR is run from "apache" repository (but in this case the pipx/packaging issue causes even the "build info" job to fail there - normally the output of that build info job is used to skipp all the other jobs in "pull request target" workflow, so you can merge it @ephraimbuddy - ignoring the "Pull request target" "build info" workflow (cc: @hussein-awala ). |
potiuk
approved these changes
Oct 8, 2023
Ok. Thanks for info |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Time for
2.7.2rc1!