-
Notifications
You must be signed in to change notification settings - Fork 64
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
[Feature]: Korifi API users can push manifests with services #2322
Comments
Issue: #2322 Co-authored-by: Kieron Browne <kbrowne@vmware.com> Co-authored-by: Georgi Sabev <georgethebeatle@gmail.com> Co-authored-by: Danail Branekov <danailster@gmail.com>
Issue: #2322 Co-authored-by: Kieron Browne <kbrowne@vmware.com> Co-authored-by: Georgi Sabev <georgethebeatle@gmail.com> Co-authored-by: Danail Branekov <danailster@gmail.com>
Issue: #2322 Co-authored-by: Kieron Browne <kbrowne@vmware.com> Co-authored-by: Georgi Sabev <georgethebeatle@gmail.com> Co-authored-by: Danail Branekov <danailster@gmail.com>
Issue: #2322 Co-authored-by: Kieron Browne <kbrowne@vmware.com> Co-authored-by: Georgi Sabev <georgethebeatle@gmail.com> Co-authored-by: Danail Branekov <danailster@gmail.com>
Issue: #2322 Co-authored-by: Kieron Browne <kbrowne@vmware.com> Co-authored-by: Georgi Sabev <georgethebeatle@gmail.com> Co-authored-by: Danail Branekov <danailster@gmail.com>
Rejecting as when the service instance referenced in the manifest does not exist korifi succeeds and does not create a service binding. Under the same conditions cf for vms is failing like this: |
For context on the issue above: When the manifest references a service that does not exist, on CF for VMs the error
|
Blockers/Dependencies
No response
Background
As of today Korifi does not support manifests with services
Acceptance Criteria
GIVEN I have create a user-provided service
s1
GIVEN I push the following manifest
THEN I see it starts successfully
AND WHEN I
cf env app
THEN I see the desired service bindings available in
VCAP_SERVICES
:Dev Notes
The text was updated successfully, but these errors were encountered: