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

systemservices/marketplace: manifest validation #829

Merged
merged 16 commits into from
Mar 29, 2019

Conversation

ilgooz
Copy link
Contributor

@ilgooz ilgooz commented Mar 19, 2019

manifest data is created by users/devs. thus, its content is not trusted and it needs to be validated. this way, it's possible to ignore any service versions that have invalid manifest data.

@ilgooz ilgooz changed the base branch from master to dev March 19, 2019 12:34
@ilgooz ilgooz force-pushed the ss-marketplace/feature/manifest-validation branch from e4480c6 to 35ff845 Compare March 19, 2019 12:43
@ilgooz ilgooz marked this pull request as ready for review March 19, 2019 12:46
@ilgooz ilgooz requested review from NicolasMahe and a team March 19, 2019 12:46
@ilgooz ilgooz force-pushed the ss-marketplace/feature/manifest-validation branch 3 times, most recently from 2ca13c3 to 47d6a3f Compare March 19, 2019 13:04
@antho1404
Copy link
Member

Just seeing this PR I was thinking why not delegating more to the system service and have the publish command that actually take the content of the manifest in the mesg.yml (like that we have the verification from the core) and the marketplace take care of sending this to IPFS. That simplifies the logic on the CLI also we could have a link between the system service and the version that the system service can actually handle

@ilgooz ilgooz force-pushed the ss-marketplace/feature/manifest-validation branch from 47d6a3f to 7d12df8 Compare March 19, 2019 22:47
package-lock.json Outdated Show resolved Hide resolved
@ilgooz ilgooz force-pushed the ss-marketplace/feature/manifest-validation branch 2 times, most recently from 77ed536 to 70ada3e Compare March 21, 2019 10:22
@ilgooz ilgooz requested review from NicolasMahe and a team March 21, 2019 10:23
systemservices/marketplace/src/contracts/manifest.ts Outdated Show resolved Hide resolved
systemservices/marketplace/src/contracts/version.ts Outdated Show resolved Hide resolved
systemservices/marketplace/src/contracts/version.ts Outdated Show resolved Hide resolved
systemservices/marketplace/gen-schema Outdated Show resolved Hide resolved
manifest data is created by users/devs. thus, its content is not trusted and it needs to be validated. this way, it's possible to ignore any service versions that have invalid manifest data.

the validation made with JSON Schemas, one created from Manifest TS type and other created manually for service's definition.

* added gen-schema command to package.json to generate JSON Schema of Manitest type.
* added package-lock.json file.
@NicolasMahe NicolasMahe self-assigned this Mar 27, 2019
NicolasMahe
NicolasMahe previously approved these changes Mar 28, 2019
NicolasMahe
NicolasMahe previously approved these changes Mar 29, 2019
…tplace/feature/manifest-validation

# Conflicts:
#	systemservices/marketplace/package-lock.json
#	systemservices/marketplace/package.json
@NicolasMahe NicolasMahe merged commit 04abd29 into dev Mar 29, 2019
@NicolasMahe NicolasMahe deleted the ss-marketplace/feature/manifest-validation branch March 29, 2019 08:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants