-
Notifications
You must be signed in to change notification settings - Fork 8
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
MERGING release/23.10 into main #245
Merged
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
Feature/otc 1080: core_user_groups name conflict fix
OTC-1082: add parent_location logic to users query
OP-1445: fix show deleted users
* OP-1360: updated django scheme and set managed to true * OP-1075: added property to check if user is imis admin --------- Co-authored-by: lruzicki <lruzicki@gmail.com>
…eted (#180) * OTC-1080: added deletion of dependent tabels before user tabel is deleted * OTC-1080: added check for pssql to delete dependent table before deleting core_user * OTC-1080: changed string to variable database name for vendor connection --------- Co-authored-by: lruzicki <lruzicki@gmail.com>
* CM-68: added register point in core to register custom filter wizards * CM-68: removed redundant import * CM-68: implemented service responsible for passing definition of filters * CM-68: improvements in solution, added docstrings for Storage/Hub class * CM-68: fixed docstring for interface method of loading definition * CM-68: moved registering filter into interested modules * CM-68: added section in README regarding custom filters * CM-68: fixed logger text message * CM-68: updated readme to add info about interface implementation * CM-68: fixed typo * CM-69: fixed registering to take objects instead of module file * CM-68: fixing creation of additional records for particular module * CM-68: fixing docsstring and readme documentations * CM-68: fixing docsstring and readme documentations part 2 * CM-68: added changes after review
#185) * CM-68: added register point in core to register custom filter wizards * CM-68: removed redundant import * CM-68: implemented service responsible for passing definition of filters * CM-68: improvements in solution, added docstrings for Storage/Hub class * CM-68: fixed docstring for interface method of loading definition * CM-68: moved registering filter into interested modules * CM-68: added section in README regarding custom filters * CM-68: fixed logger text message * CM-68: updated readme to add info about interface implementation * CM-68: fixed typo * CM-69: fixed registering to take objects instead of module file * CM-68: fixing creation of additional records for particular module * CM-68: fixing docsstring and readme documentations * CM-68: fixing docsstring and readme documentations part 2 * CM-69: added graphQL query to fetch possible way of building filters * CM-69: added mapping for field and types, minor improvements * CM-68: added changes after review * CM-69: added user authorization check in gql query for custom filters
Revert "Feature/otc 1080: core_user_groups name conflict fix"
…provided by frontend, extend export to add custom filters (#190) * CM-71: added apply_filter_to_queryset signature of method into interface * CM-71: added missing pass * CM-71: added in export mixin possibility to use custom filters * CM-71: removed redundant comment
* OTC-1098: migration that changes the type of jsonext column for tblOfficer * OTC-1098: code refactored for 0023 migration * OTC-1098: used variables instead of strings --------- Co-authored-by: lruzicki <lruzicki@gmail.com>
…orts (#191) * CM-162: improve custom filter applying into queryset in query and exports * CM-162: fixed broken tests * CM-162: revert change with fix broken test * CM-162: changed username value to more unique
* CI update * CI Update 2 * ONI-104: Block logging if HF contract expired. (#215) * ONI-104: Block logging if HF conract expired. * ONI-104: Changed default setting for HF status login. * ONI-104: Code review changes in HF contract login check. * CM-296: add additional params to the custom filters (#218) Co-authored-by: Jan <j.dolkowski@soldevelo.com> * Better helpers (#219) * cache-user-disctrict * fix * better helper * ONI-174: Fix updating user. (#220) * Deactivate cache on service (#221) * hotfix user save * ONI-174: Add util to remove permission from a role. (#223) * update cache rights (#225) --------- Co-authored-by: Damian Borowiecki <dborowiecki@soldevelo.com> Co-authored-by: Jan <jdolkowski@soldevelo.com> Co-authored-by: wzglinieckisoldevelo <98958634+wzglinieckisoldevelo@users.noreply.github.com> Co-authored-by: Jan <j.dolkowski@soldevelo.com> Co-authored-by: Patrick Delcroix <patrick.delcroix@swisstph.ch>
…#226) * CQI-80: removed setting locked password if nothing is passed in password * CQI-80: added require GET decorator into fetch_export view * CQI-80: added require GET decorator into get_scheduled_jobs * CQI-80: added require GET decorator into get_scheduled_jobs * CQI-80: revert change with password issue
OM-70: serialize user roles
Revert "OM-70: serialize user roles"
MERGING RELEASE branches
* fix prefix for validity query * fix prefix for user validity query
* fixing user liting * Update schema.py * orverload has perms * remove added line
* OP-1599: Username can be reused. * OP-1599: Changed mutation code to allow for username reuse.
Co-authored-by: Jan <j.dolkowski@soldevelo.com>
MERGING RELEASE branches
MERGING develop into release/23.10
hirensoni913
approved these changes
Jan 16, 2024
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.
MERGING release/23.10 into main