search

cloudfoundry / cli

The official command line client for Cloud Foundry
https://docs.cloudfoundry.org/cf-cli
Apache License 2.0
1.75k stars 929 forks source link

Request: cf7 push --service mydb -S mysmtp #1687

Open drnic opened 5 years ago

drnic commented 5 years ago

What's the user value of this feature request?

Currently in cf7 push(and the legacy cf6 push) a user can modify the buildpacks of the app, and a range of other attributes, but they cannot specify the service instances to bind to.

Could we please add --service and an -S alias to the cf7 push command?

Who is the functionality for?

Developers

How often will this functionality be used by the user?

All the time.

Who else is affected by the change?

No one negatively affected.

Is your feature request related to a problem? Please describe.

It is frustrating that I cannot cf7 push and specify the set of service instances to bind to.

Describe the solution you'd like

cf7 push --service mydb -service mysmtp
cf7 push --service mydb -S mysmtp
cf7 push -S mydb -S mysmtp

Describe alternatives you've considered

Currently a user must setup service bindings via app manifests or via cf7 bind-service helper.

cf-gitbot commented 5 years ago

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/166655847

The labels on this github issue will be updated when the story is started.

abbyachau commented 5 years ago

Hi @drnic we don't have any plans to add additional flags to push at the moment since binding an app to a service is supported by app manifests. I'll leave this feature request open so that users can view/comment. Thanks again for the feedback.

drnic commented 5 years ago

@abbyachau am I only allowed to request features or submit PRs for features you already plan to support? I don't understand this attitude at all that I've encountered with the CLI team this year.

drnic commented 5 years ago

Perhaps disable Issues + PRs for this project if its not OSS.

JakobFels commented 5 years ago

A workaround is to add services: ((services)) to your manifest and the use cf push --var services=[] for no services and --var services=[service1,service2] to add services.

drnic commented 5 years ago

@JakobFels thanks for that idea.

I'd still like this issue to stay open - I'd like some UX equality to exist between choosing buildpacks via cf push -- cf push -b b1 -b b2 and choosing services.

github-actions[bot] commented 1 month ago

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed.