task/WI-398: Update Allocation Onboarding Check#1299
Merged
Merged
Conversation
…tion with access to a specific machine.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1299 +/- ##
==========================================
+ Coverage 63.98% 64.01% +0.02%
==========================================
Files 461 461
Lines 13723 13733 +10
Branches 2738 2735 -3
==========================================
+ Hits 8781 8791 +10
Misses 4595 4595
Partials 347 347
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
rstijerina
reviewed
May 15, 2026
…sts will be searched. Refactored code to be more readable.
This file contains hidden or 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
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.
Overview
Added part to allocation check that validates if a user has an allocation with access to a specific machine.
Related
Changes
Adds an
expected_hostsetting to the allocation check in onboarding, and will not let the user access the portal if they do not have an allocation with access to that host.Testing
settings_default.pyorsettings_custom.py, add the snippet below to your_PORTAL_USER_ACCOUNT_SETUP_STEPS:frontera.tacc.utexas.edu. Test two or more expected hosts where you don't have access to all of them. Reset your user's onboarding steps again and the logs should let you know which hosts failed.expected_hostfrom thesettingsin the snippet, the portal should only check if you have any active allocations at all.UI
Notes