Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Feature Request: Support ZK ACLs per Profile, per Application

Open
#40 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java, spring-boot
Domain
backend, security

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.

Description

enhancement help wanted

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.

Dominant language
Java
Stars
574
Forks
407
Avg merge
11h 50m
Merged PRs (30d)
12

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from spring-cloud/spring-cloud-zookeeper

All issues in spring-cloud/spring-cloud-zookeeper

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.