Skip to content
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

[BUG] Generate manifest api schema inconsistency for services #3683

Open
Gourab1998 opened this issue Mar 16, 2024 · 0 comments
Open

[BUG] Generate manifest api schema inconsistency for services #3683

Gourab1998 opened this issue Mar 16, 2024 · 0 comments

Comments

@Gourab1998
Copy link

Issue

Generate manifest schema inconsistency for services

Context

On call to "/v3/apps/$GUID/manifest" api returns the services as array of strings when expected was array of objects.
This inconsistency creates problem for strongly typed clients.

Steps to Reproduce

cf push

applications:
- name: http-bin
  docker:
    image: kennethreitz/httpbin
  services:
  - name: xsuaa-tf
  processes:
  - type: web
    disk_quota: 1024M
    health-check-type: http
    health-check-http-endpoint: /get
    instances: 1
    memory: 256M
    readiness-health-check-type: http
    readiness-health-check-http-endpoint: /get

export GUID=$(cf app http-bin --guid)
cf curl "/v3/apps/$GUID/manifest"

---
applications:
- name: http-bin
  docker:
    image: kennethreitz/httpbin
  services:
  - xsuaa-tf
  processes:
  - type: web
    instances: 1
    memory: 256M
    disk_quota: 1024M
    log-rate-limit-per-second: -1
    health-check-type: http
    health-check-http-endpoint: "/get"
    readiness-health-check-type: http
    readiness-health-check-http-endpoint: "/get"

Expected result

I would expect the returned schema to have services as

  services:
  - name: xsuaa-tf

Current result

Currently we are getting array of strings even when we are pushing it as an array of objects.

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