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
Adds an ee_admin user to test setup #1418
Adds an ee_admin user to test setup #1418
Conversation
✅ Deploy Preview for galaxyng ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Replaces admin user use with ee_admin user Issue: AAH-1796
30903c3
to
dcae542
Compare
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.
Looks good, added a minor suggestion.
"ee_admin": { | ||
"username": "ee-admin", |
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.
you can probably make these both ee_admin
... the only reason some usernames have a dash is due to their setup in keycloak
dev/common/setup_test_data.py
Outdated
# Note: this user is not a part of ephemeral keycloak users | ||
ee_admin, _ = User.objects.get_or_create(username="ee-admin") | ||
ee_admin.set_password("redhat") | ||
ee_admin.groups.add(ee_group) | ||
ee_admin.save() |
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.
If we ever need a new test user that will also be tested in insights mode, we will want to pick a username that is already in keycloak so the test users are consistent in standalone and insights mode. For this execution environment user, I think it is ok to not match up to keycloak.
Issue: AAH-1796
What is this PR doing:
Creates an
ee_admin
user to be used in integration tests. Replaces the use of theadmin
user in thetest_api_ui_v1_execution_environments_registries
test per the TODO item.Issue: AAH-1796
Reviewers must know:
Notes:
PR Author: Add a QE reviewer (exceptions);
Reviewers: look for sound code, no code smells, docs & test coverage
Merger: When merging, include the Jira issue link in the squashed commit