-
Notifications
You must be signed in to change notification settings - Fork 3
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
ASK/Account Switch Key not working #30
Comments
Hi @amoening Could you maybe provide some more info ?
Looking to hear from you! |
I have the latest installed from homebrew
My obfuscated credentials:
I tried even specifying my conf and section and still no joy (obfuscating a bit but you get the jist)
Still gives my my default client namespace / not respecting the ASK.. I noticed an update in the common-cli-golang https://github.com/akamai/cli-common-golang/blob/master/common.go maybe this impacted your package? Im very new to GO so maybe nothing ... yea thanks for the look see! |
@amoening I looked at the repo - but the one you reffered is not one we use :) we use this one https://github.com/apiheat/akamai-cli-common/ From the get request you posted I can see it does not really add the query string required Correct one should look like ... I wonder if there is some logic that goes wrong. Could you do the following:
|
IDK if this is a credentials issue as I do have access to my base namespace, and I am getting responses from the endpoint, however still no ASK query string :( I stripped down my edgerc to simplify - So all I have in credentials is a section called "networklistcreds"
Expected failure as no credential is in default, my base setup is looking for default
Still no account-switch-key query param with request when specifying the switch and the credentials section:
Same when I switch it around and only name credentials section with "default" and dont specific the credentials::
Thanks again for taking a look! |
Hi @amoening - I think culprit of this issue is in one of the packages we depend on building the correct flags. Please take a look on https://github.com/apiheat/akamai-cli-netlist/releases/tag/v6.1.0 If you could download that version and use it as just standalone - and let me know if you can see ASK being correctly added as query string. For global fix - we need on our side make some chained changes. So depending if this will work for you we will know how much work we got :) |
OK making progress (now seeing the ask query and getting the right response / namespace but its got some funny things in the debug output ) but I think we may have an input encoding issue er something. Let me demonstrate :: Running the local updated bin
Notice the "(MISSING)" part in the URI in between the 2 aspects of the ASK key :: F-AC-XXXXXXX:Y-YYYY Maybe the ":" semicolon is getting borked somehow? It works as it is but that MISSING part has me scratching my head... Again thanks for this tool and the help! |
Hey @amoening the missing part got me really confused as well. So for a fix I need to make a PR on our common repo. The missing part is logging of the underlying http client which seems to be wrong I checked it and I have exactly the same
I have opened an issue on go-resty/resty#446 and will follow up with PR on our end |
In order to solve this we will need to upgrade to newer version of resty |
I cant seem to get the ASK/Account Switch options to take effect.
USAGE:
akamai netlist [global options] command [command options] [arguments...]
$ akamai netlist --account-switch-key "XXXXX" get all
$ akamai netlist --ask "XXXXX" get all
Responds only with what my default credential account and not my intended target switch account. I asked (pun intended) around and it seems this flag is not working as others get similar results of the netlist CLI (does not respect the ask flag).
The netlist CLI is a super easy way to manage quick updates to the lists and looking forward to getting this one fixed.
The text was updated successfully, but these errors were encountered: