Expose method and expected status code on http checks
Quality Gate passed
Kudos, no new issues were introduced!
0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication
This branch has conflicts that must be resolved
@gkze would it be possible to find some time slot to handle conflicts? thank you
Sorry for the long delay here. Yeah I can update this PR sometime by the end of this week.
Just thinking about this - I realize my fork has fallen far enough behind that it might be worth restarting the change. I see that status code was already added.
For .ValidateAndSetDefaults(), if we add an Http field alongside the HttpGet field it would be possible to have a case where both are set. There is currently no error being returned from that method. Should the signature change to check that if both are set to return an error stating that those two fields are mutually exclusive?