Respond with data to all writes in PKI engine #18222
Merged
+47
−19
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.
Signed-off-by: Alexander Scheel <alex.scheel@hashicorp.com>
As identified in #18199, several
/config
endpoints behave differently than their non-config endpoints. This can be confusing as they won't clear their data; you must manually submit defaults if that's preferable.Respond to all writes with the written data, rather than with nil responses. This lets operators see if their intended changes align with what actually occurred, without having to issue a new read.