Move internal-ghorgs to salesforce and drop `orgs.yaml`
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reading the follow-up in issue 207 and tracing how tests/repo_data/openedx/openedx-webhooks-data/orgs.yaml supplies the OSPR bot's internal-ghorgs setting. Compare that flow with salesforce-export.csv and the validation responsibilities in openedx-webhooks-data-schema. Done means internal-ghorgs is sourced from Salesforce, orgs.yaml is no longer needed, and the affected data-validation tests or repositories have an explicit outcome.
Written by the indexing model from the issue text.
Description
This is follow-up from the work done in https://github.com/openedx/openedx-webhooks/issues/207, which allowed us to delete people.yaml
The only thing we still use the manually-maintained orgs.yaml file for is the internal-ghorgs settings, which tells the OSPR bot that it can bypass automated triage process for certain "internal" entities like Axim, 2U, and Arbisoft.
If we were able to move this setting into Salesforce and pull it down from salesforce-export.csv, it would make it so all our OSPR data is is a single, auto-updating file.
Furthermore, if we can use Salesforce to validate the data, then we no longer need to run unit tests on https://github.com/openedx/openedx-webhooks-data just to validate the consistency of the data files.
Value:
- Simpler for Axim on-call to understand how this all works
- Less openedx-webhooks code to maintain
- Less potential for confusion around outdated data in orgs.yaml
- Potentially able to archive https://github.com/openedx/openedx-webhooks-data-schema/ and remove the unit tests from https://github.com/openedx/openedx-webhooks-data
- Dominant language
- Python
- Stars
- 13
- Forks
- 22
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 6
Getting set up
- Ships a 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 openedx/openedx-webhooks
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
openedx/openedx-webhooks#469 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
openedx/openedx-webhooks#391 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
openedx/openedx-webhooks#319 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
openedx/openedx-webhooks#285 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
openedx/openedx-webhooks#259 ·
Maintainers usually reply within 1 day
All issues in openedx/openedx-webhooks
Similar issues
-
opensubtitlescom: provider rejects pt-PT even though its own converter maps itPossibly taken @paulo-0308 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Diaoul/subliminal#1405 ·
-
Internal ErrorOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
frappe/frappe_docker#2071 ·
Maintainers usually reply within 1 day
-
bug python
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
traceloop/openllmetry#4717 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
The-Pocket/PocketFlow#161 ·
-
comp/desktop P2 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#157702 ·
Maintainers usually reply within 1 day