William Brafford f56eec35a5 Make feature reset API response more informative (#71240) (#72332) ... * Make feature reset API response more informative (#71240) Previously, the ResetFeatureStateStatus object captured its status in a String, which meant that if we wanted to know if something succeeded or failed, we'd have to parse information out of the string. This isn't a good way of doing things. I've introduced a SUCCESS/FAILURE enum for status constants, and added a check for failures in the transport action. We return a 207 if some but not all reset actions fail, and for every failure, we also return information about the exception or error that caused it. * Fix 7.x backport compilation issues * Feature reset integration test should tolerate failed resets (#72326) Co-authored-by: Jay Modi <jaymode@users.noreply.github.com>		2021-04-27 17:50:30 -04:00
..
features-apis.asciidoc	Add docs for feature reset API (#71759)	2021-04-21 17:41:04 -04:00
get-features-api.asciidoc	Change Get Snapshottable Features endpoint to _features (#69755)	2021-03-02 15:33:40 -07:00
reset-features-api.asciidoc	Make feature reset API response more informative (#71240) (#72332)	2021-04-27 17:50:30 -04:00