Add support for read-only JDBC URI
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
Research direction
Start by tracing how CfService credentials are exposed through Spring Boot auto-configuration, then examine whether a JdbcUrlCreator entry point already exists. Define and document an extensibility mechanism for a secondary read-only JDBC URI, supporting either a supplied URL or generated values from read-* credentials, and add coverage for the chosen behavior.
Written by the indexing model from the issue text.
Description
First off, I really like the simplicity of this new CfEnv project for parsing Cloud Foundry VCAP_SERVICES and injecting properties into spring-boot for auto-configuration. I think it has a lot of potential!
I have been trying to figure out an easy way to support an additional parameter in the credentials property of a given CfService. My specific use case is to support a read-only URI that could be used as a secondary data source, similar to what is mentioned here: https://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#howto-two-datasources.
In the best case, the jdbc-url for the secondary datasource would be provided in the service-broker/user-provided-service directly. In the worse case, the jdbc-url would have to be generated by a JdbcUrlCreator from a series of credentials.read-* properties (url/uri, host, port, username, password...) in the service-broker/user-provided-service.
Since spring-framework has no pre-defined properties for this specific use case, I'm not sure this is something that should be explicitly covered by this library. However, at the same time I feel that this library could be more accommodating to custom service-broker(s)/user-provided-service(s) credentials properties. As such, I think it's worth exploring how to support this use case through some sort of extensibility mechanism.
I am looking forward to the feedback on this and am willing to become a contributor to this project.
- Dominant language
- Java
- Stars
- 97
- Forks
- 64
- Avg merge
- 6h 36m
- Merged PRs (30d)
- 6
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the 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 pivotal-cf/java-cfenv
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
pivotal-cf/java-cfenv#354 · 1 reaction ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 48/100
pivotal-cf/java-cfenv#296 · 3 reactions ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
pivotal-cf/java-cfenv#292 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
pivotal-cf/java-cfenv#255 · 2 comments ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
pivotal-cf/java-cfenv#249 · 2 comments ·
All issues in pivotal-cf/java-cfenv
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Content
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
RunestoneInteractive/rs#1559 · 1 comment ·
Maintainers usually reply within 2 days
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
inu-appcenter/memorIN-backend#298 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
opendataloader-project/opendataloader-pdf#757 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
redhat-developer/intellij-quarkus#1626 ·