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

Expose api errors for service broker commands #465

Merged
merged 1 commit into from Jun 11, 2015

Conversation

rainmaker
Copy link
Contributor

The API was returning a 403 for unauthorized service broker operations, but the CLI was making it seem like a 404. We're now going to expose all CC errors that occur. The previous behavior is retained only for the case where there is no CC error, but the list of service brokers is empty.

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

Thanks!

Raina and @Gerg
CF Services API

- Unless it is a specific case where there was no error but there were
  also no existing service brokers

[#94892746]
@cfdreddbot
Copy link

Hey rmasand!

Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you've already signed the CLA.

@@ -135,6 +135,27 @@ var _ = Describe("Service Brokers Repo", func() {
Expect(apiErr).To(HaveOccurred())
Expect(apiErr.Error()).To(Equal("Service Broker my-broker not found"))
})

It("returns an error when listing service brokers returns an api error", func() {
Copy link
Contributor

Choose a reason for hiding this comment

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

This description reads odd... "returns... returns..."

jberkhahn added a commit that referenced this pull request Jun 11, 2015
Expose api errors for service broker commands
@jberkhahn jberkhahn merged commit e2c63ef into master Jun 11, 2015
@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/96805746.

@tanglisha tanglisha deleted the 94892746-service-brokers-403 branch June 16, 2015 17:41
savitaashture pushed a commit to savitaashture/cli that referenced this pull request Jul 31, 2020
This will fix pipeline start throwing
error on interactive input params if
the params is of type array or string
without default value

Also fix array param with default input
as the question was incorrectly asked

Fix cloudfoundry#465
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.

None yet

6 participants