feat: support exposed-service acceptance commands in hub validate#79
Open
feat: support exposed-service acceptance commands in hub validate#79
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR extends oscar-cli hub validate to better support acceptance tests for exposed services.
In oscar-cli, hub validate now understands a structured exposed HTTP acceptance step for RO-Crate metadata. The validator can execute multipart POST requests against /system/services//exposed/..., apply service Basic Auth with the OSCAR service token when required, and validate response status and media type, including ZIP payload checks. A new print-only mode, --print-acceptance-commands, renders the equivalent shell commands for each acceptance step, including the selected cluster endpoint and a command to obtain the service token from oscar-cli service get.