spring-cloud / spring-cloud/spring-cloud-zookeeper
Feature Request: Support ZK ACLs per Profile, per Application
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 574
- Forks
- 408
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 4
Description
It's often desirable to restrict visibility of application properties such that an application running in DEV can't accidentally (or otherwise) use properties from PROD, or vice versa. It would also be desirable to prevent one application from accessing the properties of another.
Zookeeper ACLs seem like the obvious choice for implementing this. It would be great if you could associate an authId and password with each profile in an application that would be used by spring-cloud-zookeeper when accessing ZK nodes.
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
No files, tests, or entry points are identified in the issue. Start by locating how spring-cloud-zookeeper accesses ZooKeeper nodes and how application profiles are configured; done means profile- and application-specific credentials enforce the requested visibility boundaries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100