Skip to content

Conversation

@benjaminguttmann-avtq
Copy link

Description of the Change

The PR makes the droplet's lifecycle information available as a property of the droplet object.

Why Is This PR Valuable?

Within cf_exporter we want to specify different actions based on which droplet lifecycle is used. Therefore we need to make that information available.

Applicable Issues

How Urgent Is The Change?

not urgent

Other Relevant Parties

Who else is affected by the change?

Copy link
Contributor

@anujc25 anujc25 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couple of comments but otherwise looks good.

It might be good to rebase this PR as well so that it can take the improvements done in the integration tests pipeline. (same comments are applicable to #3633 as well)

// An object describing the lifecycle that was used when staging the droplet
// possible values for type: "buildpack", "cnd", "docker"
type DropletLifecycle struct {
Type string `json:"name"`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we call the json tag as type instead of name here? That is how the cloud-controller api returns the response as well.

}

// An object describing the lifecycle that was used when staging the droplet
// possible values for type: "buildpack", "cnd", "docker"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// possible values for type: "buildpack", "cnd", "docker"
// possible values for type: "buildpack", "cnb", "docker"

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.

2 participants