Skip to content
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

Open
javiergarza opened this issue Apr 22, 2019 · 4 comments
Open

Upgrade to papi v1 #39

javiergarza opened this issue Apr 22, 2019 · 4 comments
Labels
bug Something isn't working

Comments

@javiergarza
Copy link

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

@zstlaw
Copy link
Contributor

zstlaw commented Mar 12, 2020

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 zstlaw closed this as completed Mar 12, 2020
@javiergarza
Copy link
Author

@zstlaw, @lukaszczerpak asked to have this issue re-opened (I will let him comment on that)

@javiergarza javiergarza reopened this Jun 25, 2020
@lukaszczerpak
Copy link

@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!

@vreddhi
Copy link

vreddhi commented Jul 29, 2020

Looks like the the latest release has fixed this.

@lkowalsk-akamai-com lkowalsk-akamai-com added the bug Something isn't working label May 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

5 participants