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(core): Switch core client in v6provider to use generated next client #127

Merged
merged 19 commits into from
Jul 4, 2024

Conversation

ikadix
Copy link
Collaborator

@ikadix ikadix commented Jun 5, 2024

Uses the new go-katapult/next/core package in the v6provider.

@ikadix ikadix changed the title chore: add CoreNext Client to meta feat(core): Switch core client in v6provider to use generated next client Jun 5, 2024
@ikadix ikadix requested a review from jimehk June 5, 2024 13:30
@ikadix ikadix marked this pull request as ready for review June 5, 2024 13:31
internal/v6provider/resource_load_balancer.go Outdated Show resolved Hide resolved
internal/v6provider/meta.go Outdated Show resolved Hide resolved
internal/v6provider/resource_load_balancer_rule.go Outdated Show resolved Hide resolved
internal/v6provider/resource_ip.go Show resolved Hide resolved
internal/v6provider/meta.go Outdated Show resolved Hide resolved
internal/v6provider/meta.go Outdated Show resolved Hide resolved
internal/v6provider/meta.go Outdated Show resolved Hide resolved
@ikadix ikadix requested a review from jimehk July 3, 2024 15:14
@ikadix ikadix merged commit d313927 into main Jul 4, 2024
17 checks passed
@ikadix ikadix deleted the 121_switch_to_new_client branch July 4, 2024 12:26
@replease replease bot mentioned this pull request Jul 4, 2024
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