Provide public API to remove registered policy providers
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 62/100
Research direction
Start by locating the public API for policy providers and the lib ctx provider registry. Trace how providers are registered and identified, then add the corresponding removal entry point and tests showing that a provider can be removed by ID and is no longer available.
Written by the indexing model from the issue text.
Description
Currently, public API has no way to remove a registered policy provider from a lib ctx. There should be a function to remove a policy provider by ID.
- Dominant language
- C
- Stars
- 16
- Forks
- 9
- Avg merge
- 4h 46m
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NASA-AMMOS/BSL
-
BIB validator rejects BIB targeting the primary block (block 0), deleting the bundle at sourcePossibly taken @jeronstone claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
NASA-AMMOS/BSL#373 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Policy query leaks host primary block (BSL_PrimaryBlock_deinit skipped) on two early-exit pathsPossibly taken @jeronstone claimed this 8 days ago. Openbug CRIT-3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NASA-AMMOS/BSL#355 · 3 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
CMake warnings about deprecated behaviorsPossibly taken @BrianSipos claimed this 7 days ago. Opensustainment
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
NASA-AMMOS/BSL#282 · 1 assignee ·
Maintainers usually reply within 1 day
-
sustainment
Difficulty 4/5 3-5 days Newbie friendliness 40/100
NASA-AMMOS/BSL#372 ·
Maintainers usually reply within 1 day
-
bug CRIT-3
Difficulty 3/5 Half a day Newbie friendliness 35/100
NASA-AMMOS/BSL#371 ·
Maintainers usually reply within 1 day
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
valkey-io/valkey#4979 · 1 reaction ·
Maintainers usually reply within 2 days
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
cherries-works/pulse#76 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
colbymchenry/codegraph#2770 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
FriendsofECCE/ECCE#425 ·