[fix] restore settings check result unmarshaling from stderr#750
Draft
[fix] restore settings check result unmarshaling from stderr#750
Conversation
Signed-off-by: Artem Kuleshov <artem.kuleshov@flant.com>
Signed-off-by: Artem Kuleshov <artem.kuleshov@flant.com>
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.
Overview
Use errors.As with executor.StderrError to extract structured validation results from hook stderr. When the hook exits with code 1 and stderr contains JSON, it is unmarshaled into settingscheck.Result. Non-stderr errors are propagated as before. Depends on shell-operator StderrError and module-sdk exit code fix.
Its related with module-sdk-pr and shell-operator-pr
What this PR does / why we need it
Special notes for your reviewer