Backport of UI/add allowed response headers secret mount into release/1.13.x #19222
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.
Backport
This PR is auto-generated from #19216 to be assessed for backporting due to the inclusion of the label backport/1.13.x.
The below text is copied from the body of the original PR.
Adds
allowed_response_headers
to mount config for secret engines. docs. Allows things likeLast-Modified
as a header to be on responses to fetching pki CA/CRLs.Also updates empty state to include the item type in the message, instead of just 'Secret' for each tab
PKI empty state:
transit:
### transform: ![Uploading Screenshot 2023-02-16 at 7.49.21 AM.png…]()
Overview of commits