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

Add appGUID attribute to droplet resource #2837

Closed

Conversation

gmllt
Copy link
Member

@gmllt gmllt commented Mar 28, 2024

Where this PR should be backported?

Description of the Change

The V3 API allows you to access to the relationships existing beween a droplet and its related app.
This PR make this relationship visible trough a new AppGUID attribute in the resource droplet.

The community cf_exporter currently use the /v2/spaces/:guid/summary endpoint to gain access to buildpack associated to an application. Have this relationship visible would help get rid of calls on this endpoint and retrieve buildpacks attached to an application through its droplets.

This feature is necessary for applications using the cli product in go development to established relationship between an application resource and its droplets.

This feature will not cause breaking change.

@gmllt gmllt changed the title add appGUID to droplet resource Add appGUID attribute to droplet resource Mar 28, 2024
@gururajsh
Copy link
Member

@gmllt We had some environment issues and integration tests did not run. Can you please update the branch and reopen the PR?

@adamspd
Copy link

adamspd commented May 17, 2024

It would be great if we could merge this. It would take some of the work off my hands.

@gmllt gmllt force-pushed the add-droplets-relationships-main branch from 0a28232 to 7f1b0e0 Compare May 17, 2024 12:46
@gmllt
Copy link
Member Author

gmllt commented May 17, 2024

creating new PR

@gmllt
Copy link
Member Author

gmllt commented May 17, 2024

new PR : 2933

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

Successfully merging this pull request may close these issues.

3 participants