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

[instruments/instrument_manager] Migrate instrument permissions from config.xml to database #8302

Merged
merged 13 commits into from
Mar 15, 2023

Conversation

driusan
Copy link
Collaborator

@driusan driusan commented Dec 21, 2022

This migrates instrument permissions from the config.xml to the database in a new testnames_permissions_rel table. The table can be managed from the frontend in the instrument_manager module by any user who has the instrument_manager_write permission. The script tools/single_use/migrate_instrument_permissions.php can be used by existing projects to migrate their permissions from the config.xml to the new table.

@driusan driusan added Release: Add to release notes PR whose changes should be highlighted in the release notes Category: Feature PR or issue that aims to introduce a new feature Cleanup PR or issue introducing/requiring at least one clean-up operation Language: PHP PR or issue that update PHP code Language: Javascript PR or issue that update Javascript code labels Dec 21, 2022
@driusan driusan force-pushed the InstrumentPermisssionsDatabase branch from ef7ac69 to 96a1d1a Compare December 21, 2022 16:13
@driusan
Copy link
Collaborator Author

driusan commented Dec 21, 2022

Blocked by #8290

@driusan driusan added the State: Blocked PR or issue awaiting an external event such as the merge or another PR to proceed label Dec 21, 2022
@ridz1208 ridz1208 self-assigned this Feb 14, 2023
@ridz1208 ridz1208 added the State: Needs rebase PR that needs to be rebased to proceed (conflicts, wrong branch...) label Feb 14, 2023
Makefile Outdated
Comment on lines 58 to 59
instrument_manager:
target=instrument_manager npm run compile
Copy link
Collaborator

Choose a reason for hiding this comment

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

is this a leftover or are we adding this for every module now?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I've been adding it for modules when I work on them because it makes life easier but haven't systematically added every module.

docs/config/config.xml Outdated Show resolved Hide resolved
@driusan driusan force-pushed the InstrumentPermisssionsDatabase branch from ab717a8 to b28ce82 Compare February 21, 2023 19:48
@driusan driusan removed State: Needs rebase PR that needs to be rebased to proceed (conflicts, wrong branch...) State: Blocked PR or issue awaiting an external event such as the merge or another PR to proceed labels Feb 22, 2023
@laemtl laemtl added this to the 25.0.0 milestone Feb 28, 2023
@driusan
Copy link
Collaborator Author

driusan commented Mar 8, 2023

Note: this will need to be rebased/re-tested after #8422 in case of conflicts with the instrument manager

@ridz1208 ridz1208 removed their assignment Mar 15, 2023
@driusan driusan force-pushed the InstrumentPermisssionsDatabase branch from 88b56c1 to 28bf6cf Compare March 15, 2023 17:18
@driusan driusan merged commit 7cb33cf into aces:main Mar 15, 2023
@driusan driusan added the Release: Breaking changes PR that contains changes that might impact the code or accepted practices of active projects label Mar 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: Feature PR or issue that aims to introduce a new feature Cleanup PR or issue introducing/requiring at least one clean-up operation Language: Javascript PR or issue that update Javascript code Language: PHP PR or issue that update PHP code Release: Add to release notes PR whose changes should be highlighted in the release notes Release: Breaking changes PR that contains changes that might impact the code or accepted practices of active projects
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants