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

feat: update get_content_metadata_for_customer to use v2 endpoint #316

Merged
merged 1 commit into from
Nov 18, 2024

Conversation

pwnage101
Copy link
Contributor

ENT-9410

@@ -16,7 +16,7 @@ class EnterpriseCatalogApiClient(BaseOAuthClient):
"""
API client for calls to the enterprise service.
"""
api_base_url = urljoin(settings.ENTERPRISE_CATALOG_URL, 'api/v1/')
api_base_url = urljoin(settings.ENTERPRISE_CATALOG_URL, 'api/v2/')
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need every v1 endpoint in enterprise-catalog to have a functional v2 version (even if using the same exact logic as v1)?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope, I was thinking of elaborating on this by adding a constructor argument to ask for the API version.

@pwnage101 pwnage101 force-pushed the pwnage101/ENT-9410 branch 3 times, most recently from baa375a to 7f239c1 Compare November 14, 2024 21:47
@pwnage101 pwnage101 marked this pull request as ready for review November 14, 2024 22:06
@pwnage101 pwnage101 changed the title feat: Update catalog API client to use v2 endpoints feat: update get_content_metadata_for_customer to use v2 endpoint Nov 14, 2024
@pwnage101 pwnage101 merged commit 3cd53a6 into main Nov 18, 2024
7 checks passed
@pwnage101 pwnage101 deleted the pwnage101/ENT-9410 branch November 18, 2024 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants