-
Notifications
You must be signed in to change notification settings - Fork 13.8k
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
Add airflow upgrade-check command (MVP) (v1-10-test) #9467
Add airflow upgrade-check command (MVP) (v1-10-test) #9467
Conversation
238d841
to
2f17299
Compare
4f848da
to
e0bdf95
Compare
845bcbe
to
90446e5
Compare
c644d53
to
5a54173
Compare
formatted_results = [self._info_from_rule_status(rs) for rs in rule_statuses] | ||
with open(self.filename, "w+") as output_file: | ||
json.dump(formatted_results, output_file, indent=2) | ||
print("Saved result to: {}".format(self.filename)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Example result
[
{
"rule": "MokcRule",
"title": "title",
"messages": [
"msg1",
"msg2"
]
}
]
Ok, no idea how to make the test runnable on CI. Two days I had only py3.5 failing, know everything is cancelled... @potiuk any ideas? |
@mik-laj @kaxil @dimberman @ashb please take a look, the CI is green and I think we are good to merge it |
Thanks @ashb, I will just rebase the PR as I spotted the Dataproc HTTP commit here |
@@ -337,7 +337,7 @@ def cancel(self, project_id, job_id, region='global'): | |||
projectId=project_id, | |||
region=region, | |||
jobId=job_id | |||
) | |||
).execute(num_retries=self.num_retries) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah this one
Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
6024b48
to
c9912bb
Compare
@turbaszek @mik-laj is this still a draft? Should I merge this into 1.10.13? |
@dimberman I think we should include to in "last" 1.10 release. Currently there's only one rule implemented so not a big gain |
Co-authored-by: Tomek Urbaszek <tomasz.urbaszek@polidea.com> Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
Co-authored-by: Tomek Urbaszek <tomasz.urbaszek@polidea.com> Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com> (cherry picked from commit 2904810)
Co-authored-by: Tomek Urbaszek <tomasz.urbaszek@polidea.com> Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com> (cherry picked from commit 2904810)
This is a DRAFT and I still have to complete the missing documentation and unit tests.
I wanted to prepare a minimal valuable product for the upgrade_check command. Only one rule is implemented, but I think that's enough to show the feature. In the next steps, we can think about what rules we need to create, create tickets, and then work on the next rules by the whole community.
Recently, we have a lot of new beginner contributors and I think we can try to engage them for this task. Most rules will be small and independent, so they will be great candidates for good-first-issue.
An example of the result of this command is presented in the termianlshot below
![Screenshot 2020-06-13 at 12 58 38](https://user-images.githubusercontent.com/12058428/84566968-a63cc200-ad75-11ea-870b-60d07d0c44fa.png)
Example JSON:
Part of: #8765
Continuation of the change, but for 1.10: #9276
Make sure to mark the boxes below before creating PR: [x]
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.
Read the Pull Request Guidelines for more information.