HaztrakProfile for managing Remote signer access #637
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
The HaztrakProfile will act as the new user base profile, while the RcraProfile is relegated to only storing a user's RCRAInfo user/profile information. This moves us towards a reference implementation for the Remote Signer Policy. update pre-commit to use ruff formatter and remove black SitePermission model which represents what role based access a haztrak user has that will dictate what a user is allowed to do
…(HaztrakProfile). We moved the RcraProfile state to a sub object of the user's Profile state rename rcraProfileSlice to profileSlice, add HaztrakProfile to RcraProfile redux toolkit slice
…crasitepermissions now a user will only see the tables that the admin has given them access to
…date test suites with new preloaded state that reflects our new global state structure. adjust structure of the profile slice to use the 'sites' field to store a record of sites a user has access to in Haztrak (instead of just relying on what sites a user has access to in RCRAInfo)
…rakProfile model instance of their RcraProfile
attach admin rcrainfo profile to a haztrak site instead of the user's profile rename last_sync_date to last_rcrainfo_manifest_sync to be more clear on what is being synced add properties to haztrak profile to use an admin's rcrainfo profile rename last_rcra_sync to last_rcrainfo_manifest_sync for clarity
… connected to a user's haztrak profile) versus the old RcraSitePermissions which was dependent on a user's RCRAInfo permissions rename RcraSitePermission to RcraSitePermissions, add development fixtures, when syncing a user's RCRAInfo profile, it does not create new HaztrakSites (only RcraSites) convert foreign key to HaztrakSite to RcraSite in the RcraSitePermission (makes sense when you write it our) now we will be implementing the Remote Signer policy into our application so access will be granted by a remote signer (or the Haztrak Admin) rename 'Site' model to 'HaztrakSite' to distinguish it from the 'RcraSite' model
admin_rcrainfo_profile from HaztrakProfile
github-actions
bot
added
client
dpgraham4401
changed the title
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.
Description
This is a relatively big PR that includes the following...
HaztrakProfileORM model which now serves as the users central profileSitePermissionsORM model which contains the RBAC that a user has to a given haztrak site.These models take the existing role of the
RcraProfileandRcraSitePermissionsmodels. These models where dependent on the user's RCRAInfo profile information. These were implemented before the e-Manifest Remote Signer Policy.it also implements the following
RcraSitePermissiontoRcraSitePermissions, and use the term "RCRAInfo" to indicate that a model or object is from rcrainfo versus a haztrak defined model/object.HaztrakProfileand relegate theRcraProfileto a sub-fieldHtApiwhich is just an object with a number of functions for doing just that. This starts the work fr refactor client side logic into services #634Issue ticket number and link
Checklist