Skip to content

Update extensibility docs for connectors #439

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bart-vmware merged 6 commits into from
May 11, 2026
Merged

Update extensibility docs for connectors #439

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
91c12c9
Update extensibility docs for connectors
bart-vmware Apr 24, 2026
5ff747f
Review feedback
bart-vmware May 6, 2026
665d7e4
Fix spelling
bart-vmware May 6, 2026
2c6cfa9
Revert "Fix spelling"
bart-vmware May 7, 2026
ce1ba28
Apply suggestions from code review
bart-vmware May 7, 2026
00a142d
Add line break
bart-vmware May 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/docs/v4/connectors/extensibility.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ Steeltoe Connectors cover a fixed set of supported data stores and messaging sys
They are not open-ended plug-ins; extensibility means shaping platform credentials into the connection strings external drivers for those built-in connectors already understand.

Connectors map credentials from [Cloud Foundry service bindings](https://techdocs.broadcom.com/us/en/vmware-tanzu/platform/elastic-application-runtime/10-3/eart/binding-credentials.html) and
[Service Binding Spec for Kubernetes](https://github.com/servicebinding/spec#well-known-secret-entries) into configuration keys starting with `steeltoe:service-bindings` and merge them with local settings from `Steeltoe:Client`.
[Service Binding Spec for Kubernetes](https://github.com/servicebinding/spec#well-known-secret-entries) into configuration keys starting with `steeltoe:service-bindings` and merges them with local settings from `Steeltoe:Client`.
Comment thread
TimHess marked this conversation as resolved.
Outdated
Each connector runs the binding logic for its own service type.

Comment thread
bart-vmware marked this conversation as resolved.
To use a third-party `VCAP_SERVICES` structure, populate the `steeltoe:service-bindings` keys yourself.
Expand Down
Loading