Add support to anms-core for multiple dynamic configuration and service connection strategies
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 2
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 2
Description
Allow for an administrative REST API and supporting logic for responding to service failures with cascading fallback strategies (e.g. logging to files while OpenSearch is disconnected and recovering), as well as updating service connections based on configuration updates. When changes are made or fallbacks are applied this should be a cause for notifications and logging, so that administrators understand when an issue has occurred and if there is anything that is needed in response.
Contributor 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.
Research direction
Start by reviewing anms-core and the existing service-connection and configuration entry points, then determine how the requested administrative REST API fits into them. Done means supporting dynamic configuration updates, cascading service-failure fallbacks, and administrator notifications and logging for changes or recovery needs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100