You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please fill out the issue checklist below and provide ALL the requested information.
I reviewed open and closed github issues that may be related to my problem.
I tried updating to the latest version of the CF CLI to see if it fixed my problem.
I attempted to run the command with CF_TRACE=1 to help debug the issue.
I am reporting a bug that others will be able to reproduce.
Describe the bug and the command you saw an issue with
With cf cli v8, the command cf share-service srv-name -o org -s space fails (FAILED) and exits with 1 if the service is already shared with the org/space
Until recently, it just reported that it is already shared (OK) and ended with exitcode 0.
Looking at other cli commands like e.g. cf create-service, I'm under he impression that for idempotence reasons, commands that would only try to produce a state that already exists should not fail.
What happened
Gitlab pipelines fail all of a sudden due to new version of cf cli tools
Expected behavior
Pipelines should continue to work. If failing is going to be the new behaviou (to which I'd highly disagree!), it should at least be mentioned in the documentation (that does not make any mention of exit codes at all). Furthermore, there is no possibility to find out if a sharing is already in place except by grepping the output of cf service...
Exact Steps To Reproduce
Steps to reproduce the behavior; include the exact CLI commands and verbose output:
Run cf share-service srv-name -o org -s space on a service that is already shared with the named org/space
See error
The text was updated successfully, but these errors were encountered:
Please fill out the issue checklist below and provide ALL the requested information.
CF_TRACE=1
to help debug the issue.Describe the bug and the command you saw an issue with
With cf cli v8, the command
cf share-service srv-name -o org -s space
fails (FAILED) and exits with 1 if the service is already shared with the org/spaceUntil recently, it just reported that it is already shared (OK) and ended with exitcode 0.
Looking at other cli commands like e.g. cf create-service, I'm under he impression that for idempotence reasons, commands that would only try to produce a state that already exists should not fail.
What happened
Gitlab pipelines fail all of a sudden due to new version of cf cli tools
Expected behavior
Pipelines should continue to work. If failing is going to be the new behaviou (to which I'd highly disagree!), it should at least be mentioned in the documentation (that does not make any mention of exit codes at all). Furthermore, there is no possibility to find out if a sharing is already in place except by grepping the output of
cf service
...Exact Steps To Reproduce
Steps to reproduce the behavior; include the exact CLI commands and verbose output:
cf share-service srv-name -o org -s space
on a service that is already shared with the named org/spaceThe text was updated successfully, but these errors were encountered: