Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Add service_id to legacy_service_get api calls #2

Merged
merged 1 commit into from

3 participants

jfarrell Matt Reider cf-frameworks
jfarrell

Adds the service_id to legacy_service_get calls in order to allow
for service lifecycle api calls to be available from vmc.

jfarrell jfarrell Add service_id to legacy_service_get api calls
Adds the service_id to legacy_service_get calls in order to allow
for service lifecycle api calls to be available from vmc.
91d1105
Matt Reider

I put the analysis and merging of this pull request as a chore in our engineering team's backlog.

Matt Reider

Sounds like I can close this pull request...

Matt Reider mreider closed this
Matt Reider mreider reopened this
Matt Reider

D'oh sorry, wrong closure :)

jfarrell

we leverage this in order to talk to the legacy services lifecycle api's since there is no way currently to call this set of services by alias. Hopefully this is being taken into consideration for the cc_ng (if needed happy to help add this functionality to the cc_ng)

cf-frameworks cf-frameworks merged commit 98b1fd8 into from
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Feb 14, 2013
  1. jfarrell

    Add service_id to legacy_service_get api calls

    jfarrell authored
    Adds the service_id to legacy_service_get calls in order to allow
    for service lifecycle api calls to be available from vmc.
This page is out of date. Refresh to see the latest.
Showing with 1 addition and 0 deletions.
  1. +1 −0  cloud_controller/app/models/service_config.rb
1  cloud_controller/app/models/service_config.rb
View
@@ -204,6 +204,7 @@ def provisioned_by?(user)
# Returned for calls from legacy clients
def as_legacy
{ :name => self.alias,
+ :service_id => self.name,
:type => self.service.synthesize_service_type,
:vendor => self.service.name,
:provider => self.service.provider || "core",
Something went wrong with that request. Please try again.