-
Notifications
You must be signed in to change notification settings - Fork 76
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
Property getter with --apihost
argument modifies configuration
#95
Comments
i opened an issue against the functions plugin for this issue |
@joe4dev This issue should be fixed now but I cannot close this issue :) |
I can test it when 1.0.35 is released. |
0.19.0 is for ibm cloud cli.
I was talking about this:
https://cloud.ibm.com/docs/openwhisk?topic=cloud-functions-cli_versions
Current we are at 1.0.34 and 1.0.35 is coming in 1-2 days.
Simple do this to upgrade to 1.0.34:
bx plugin repo-plugin cloud-functions
bx plugin install cloud-functions
----- Original message -----From: Joel Scheuner <[email protected]>To: IBM-Cloud/ibm-cloud-cli-release <[email protected]>Cc: steven0711dong <[email protected]>, Comment <[email protected]>Subject: [EXTERNAL] Re: [IBM-Cloud/ibm-cloud-cli-release] Property getter with `--apihost` argument modifies configuration (#95)Date: Tue, Oct 8, 2019 4:41 AM
I can test it when 1.0.35 is released.Currently, 0.19.0 is the latest version: https://github.com/IBM-Cloud/ibm-cloud-cli-release/releases
—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or mute the thread.
|
I can confirm that this issue is fixed now in PS: The docs are not yet updated for |
whisk CLI version 2019-05-30T22:04:28+00:00
The property getter
ibmcloud fn property get --apihost
actually changes the whisk API host property.Example changing to an empty string (because I intend to query apihost and the space between the raw output flag is interpreted as empty string):
Example changing to arbitrary values:
This behavior is extremely confusing and unexpected.
Probably related to apache/openwhisk-cli#435
and also to apache/openwhisk-cli@23de5a3
Notice that the same buggy behavior does not happen in the latest
76203e8
open source version ofwsk
:The text was updated successfully, but these errors were encountered: