Provide overrides for proxy.properties in Docker deployments
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
- docker, java, kubernetes
- Domain
- devops, infrastructure
Research direction
Read the existing proxy.properties handling and Docker deployment entry points, then review pull request #20 and the accumulo-docker documentation. Done means the repository has an agreed, documented way to supply proxy properties in Docker, compose, or Kubernetes deployments, with the scope confirmed by maintainers.
Written by the indexing model from the issue text.
Description
@keith-turner and I briefly touched upon allowing proxy.properties to be overidden for a Docker instantiation of accumulo-proxy in this pull request: https://github.com/apache/accumulo-proxy/pull/20
Currently in accumulo-docker you can override properties by the following:
export ACCUMULO_CL_OPTS="-o prop.1=var1 -o prop.2=var2"
docker run -d --network="host" accumulo monitor $ACCUMULO_CL_OPTS
This is documented in the docs here: https://github.com/apache/accumulo-docker
For standard docker approaches I would say this is a simplistic mechanism that works really cleanly however if you start to look at things like docker-compose or kubernetes I would say it would be advantageous to avoid overriding the CMD or ENTRYPOINT flags where possible.
An alternative method would be to provide these as environment variables, therefore you could also use the Kubernetes secret APIs to handle things such as passwords and either map them to a file or environment variable for use within the application.
Would this be acceptable? If so I'm also happy to look at providing the same change to accumulo-docker to retain consistency?
- Dominant language
- Java
- Stars
- 11
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from apache/accumulo-proxy
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
apache/accumulo-proxy#91 · 1 comment · 1 reaction ·
-
bug
Difficulty 5/5 Over a week Newbie friendliness 35/100
apache/accumulo-proxy#32 · 6 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
apache/accumulo-proxy#22 · 10 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 30/100
apache/accumulo-proxy#10 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
apache/accumulo-proxy#7 · 6 comments ·
All issues in apache/accumulo-proxy
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
liquid-java/liquidjava#321 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
OpenConext/OpenConext-access#1015 ·
Maintainers usually reply within 1 day
-
68000: FDBcc branch target is 2 bytes too low (uses inst_start+2 instead of the displacement word)Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
NationalSecurityAgency/ghidra#9702 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
apache/rocketmq-dashboard#5358 ·
Maintainers usually reply within 3 days