spring-cloud / spring-cloud/spring-cloud-config
composite vault setup with different namespace
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2k
- Forks
- 1.3k
- Avg merge
- 2d 59m
- Merged PRs (30d)
- 16
Description
1Describe the bug
I am trying to access the HTTP header property X-Vault-namespace from my clienthttprequestinterceptor but since this field is added after the vaultclient createnamespace is executed. how can I force to execute my custom clienthttprequestinterceptor to get execute at the last
Sample
spring:
cloud:
config:
server:
composite:
- type: vault
namespace: /xyz/abc
// other properties related to the vault
- type: vault
namespace: /alpha/beta
// other properties related to the vault
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the composite Vault setup with the two namespaces shown in the issue, then trace when the clientHttpRequestInterceptor runs relative to VaultClient namespace creation. Done means the custom interceptor executes after the X-Vault-namespace header is added for both Vault entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100