TFVP-Initial-Implementation-Sys-Backend-headers#2842
Open
itsjiyapatel wants to merge 9 commits intomainfrom
Open
TFVP-Initial-Implementation-Sys-Backend-headers#2842itsjiyapatel wants to merge 9 commits intomainfrom
itsjiyapatel wants to merge 9 commits intomainfrom
Conversation
| stringplanmodifier.RequiresReplace(), | ||
| }, | ||
| }, | ||
| consts.FieldValues: schema.ListAttribute{ |
Contributor
There was a problem hiding this comment.
I think we can switch this to Set attribute type which would help ignore duplicates.
Added references to pull requests for new resource and improvements.
…ders' of github.com:hashicorp/terraform-provider-vault into VAULT-43336-TFVP-Initial-Implementation-Sys-Backend-headers
fb1ff78 to
373beae
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new Terraform Plugin Framework resource to manage Vault UI response headers via sys/config/ui/headers, providing a dedicated alternative to vault_generic_endpoint for security/CORS/custom headers.
Changes:
- Introduces
vault_config_ui_headerresource with CRUD, import-by-name, and Vault version gating. - Registers the new resource in the framework provider and adds shared constant
FieldValues. - Adds website documentation, acceptance tests, and a CHANGELOG entry.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 8 comments.
Show a summary per file
| File | Description |
|---|---|
| website/docs/r/config_ui_header.html.md | New resource documentation and examples for UI headers |
| internal/vault/sys/config/ui_header.go | New TF Plugin Framework resource implementation for UI header CRUD/import |
| internal/vault/sys/config/ui_header_test.go | Acceptance tests for create/update/import behavior |
| internal/provider/fwprovider/provider.go | Registers the new resource with the framework provider |
| internal/consts/consts.go | Adds FieldValues constant used by the new resource/tests |
| CHANGELOG.md | Adds an Unreleased FEATURES entry for the new resource |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
harshit-nema
reviewed
Apr 8, 2026
Contributor
harshit-nema
left a comment
There was a problem hiding this comment.
Review comments provided for sys backend headers.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Implements a new Terraform resource vault_config_ui_header for managing custom HTTP headers in the Vault UI. This provides a type-safe, user-friendly alternative to using vault_generic_endpoint for configuring security headers, CORS policies, and custom organizational headers.
Resource: vault_config_ui_header at internal/vault/sys/config/ui_header.go
Checklist
Output from acceptance testing:
Community Note
PCI review checklist
I have documented a clear reason for, and description of, the change I am making.
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.