Skip to content

Conversation

@moorereason
Copy link
Collaborator

When attempting to match a JSON path for initial setup, it would be
helpful to know where the path failed. This change logs the failed
parameter node. For example, if you are trying to match path "a.b.d.e",
but you failed to include the "c" node, webhook will log an error
"parameter node not found: d.e" to assist in troubleshooting.

When attempting to match a JSON path for initial setup, it would be
helpful to know where the path failed. This change logs the failed
parameter node. For example, if you are trying to match path "a.b.d.e",
but you failed to include the "c" node, webhook will log an error
"parameter node not found: d.e" to assist in troubleshooting.
@moorereason
Copy link
Collaborator Author

I crafted this PR rather quickly, so it may need some fine tuning. I was setting up a new webhook instance today that was validating several values, and I couldn't figure out why it wasn't passing. Turned out to be a missing node in one of the payload paths that I was overlooking. This PR helped me find the oversight.

@moorereason moorereason added this to the 2.7.0 milestone Dec 31, 2019
@moorereason moorereason requested a review from adnanh December 31, 2019 04:05
@moorereason
Copy link
Collaborator Author

@adnanh,
Looking at this now, I think I put too much change into a single commit. Would it help to break this PR into smaller commits?

@adnanh
Copy link
Owner

adnanh commented Feb 14, 2020

@moorereason Nah, looks good to me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants