-
Notifications
You must be signed in to change notification settings - Fork 927
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
Issue with diego enabler v1.2.2 #997
Comments
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/133977247 The labels on this github issue will be updated when the story is started. |
Looks like a duplicate of cloudfoundry-attic/Diego-Enabler#6. |
savitaashture
pushed a commit
to savitaashture/cli
that referenced
this issue
Jul 31, 2020
debbuild is using base dir for its name and not using the control file, let's rename then from cli to tektoncd-cli Closes cloudfoundry#997 Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Command
cf enable-diego some-app
What occurred, incl. error and/or stack trace
What you expected to occur
Expected a message saying diego was enabled
CLI Version
6.22.2
CC API Endpoint Version
2.63.0
Platform & Shell Details
An errand VM on a bosh director of version 1.3215.3.0
Any other relevant information
You can see in the output that diego was successfully enabled, but the response could not be parsed. One of the intermediate responses is a 400 status.
The text was updated successfully, but these errors were encountered: