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

Enable the 'Is Active?' flag by default in user view #37507

Merged
merged 2 commits into from
Feb 17, 2024

Conversation

amoghrajesh
Copy link
Contributor

While personally creating an user from the UI, I personally find it inconvenient to tick the checkbox for Is Active?
It would be nice to have this enabled by default so that users do not run into cases where they miss it


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an 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 a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

Copy link
Member

@hussein-awala hussein-awala left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to fix the tests, but +1 for this change

@jscheffl jscheffl merged commit 68e20aa into apache:main Feb 17, 2024
58 checks passed
Taragolis added a commit to Taragolis/airflow that referenced this pull request Feb 17, 2024
potiuk pushed a commit that referenced this pull request Feb 17, 2024
potiuk added a commit to potiuk/airflow that referenced this pull request Feb 18, 2024
Since all the USER/ROLE related code moved to FAB, we should also
move the user schema tests as well. Not having the tests in the
provider code, made the apache#37507 succeed because of selective chekcs
(false positive). Mobing the tests to fab provider should fix the
problem.
potiuk added a commit that referenced this pull request Feb 18, 2024
Since all the USER/ROLE related code moved to FAB, we should also
move the user schema tests as well. Not having the tests in the
provider code, made the #37507 succeed because of selective chekcs
(false positive). Mobing the tests to fab provider should fix the
problem.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants