Skip to content

Add support for file based service bindings #28

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.

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

Open
beyhan opened this issue Apr 3, 2025 · 0 comments
Open

Add support for file based service bindings #28

beyhan opened this issue Apr 3, 2025 · 0 comments

Comments

@beyhan
Copy link

beyhan commented Apr 3, 2025

There is a limit regarding the size of environment variables described in this CF issue, that is why in RFC-0030 the CF community decided to introduce a different option for service binding provisioning in the application container which is file based. The RFC describes two ways to provide the bindings in the app container one based on the K8s specification and another one providing the VCAP_SERVICES content as file, which location is specified with the VCAP_SERVICES_FILE_PATH environment variable. The feature is already available in CF and more details can be found in cloudfoundry/community#901

The go-cfenv client should add support to read service binding information from a file defined by the VCAP_SERVICES_FILE_PATH environment variable. With this users would be able to switch between VCAP_SERVICES environment variable or the VCAP_SERVICES_FILE_PATH activated via the app-feature file-based-vcap-services without the need to do any application changes other then using the go-cfenv version which supports this. I don't think that adding support for the K8s specification makes sense because a translation in the go-cfenv library from K8s specification to VCAP_SERVICES isn't possible as discussed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant