-
Notifications
You must be signed in to change notification settings - Fork 22
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
Upgrade to papi v1 #39
Comments
This is actually for internal purposes. In the end both papi v0 and v1 are currently served by the same implementation but the /v1 implementation is only present on external edge services. So for internal early stage testing v0 must be used. |
@zstlaw, @lukaszczerpak asked to have this issue re-opened (I will let him comment on that) |
@javiergarza That was the initial diagnosis.. but I got same information that papi v0 and v1 us the same implementation under the hood. From my perspective there is no issue and based on the information above it's safe to close it. Thanks! |
Looks like the the latest release has fixed this. |
Seems https://github.com/akamai/cli-property-manager/blob/master/src/papi.js is referencing calls to PAPI v0 which seems to be in BETA, while PAPI v1 is in GA. It should be relatively simple to migrate to v1
The text was updated successfully, but these errors were encountered: