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

Feat: Service Runner needs to support resolving bad Manifest files #212

Open
zcstarr opened this issue Oct 11, 2019 · 0 comments
Open

Feat: Service Runner needs to support resolving bad Manifest files #212

zcstarr opened this issue Oct 11, 2019 · 0 comments
Assignees
Labels

Comments

@zcstarr
Copy link
Contributor

zcstarr commented Oct 11, 2019

Currently discrepancies between the manifest file and services can cause listing services to break. More importantly service runner needs a safe way for users to uninstall packages, and flag configuration mismatch packages.

The use case is installing a package, updating config so the package no longer exists, then attempting to show that there is a mismatch that is problematic. This would allow service runner ui implementors to expose a way for clients to rectify the issue, by uninstalling or finding a suitable configuration.

This will become more important when the specification for a decentralized service registry is created.

Expected behavior is as follows.
A programatic uninstall api
A programatic possibly RPC available configuration mismatch api
listService ignores missing service configurations

@zcstarr zcstarr self-assigned this Oct 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant