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

Switch to go-katapult@next in new Provider Framework implementation #121

Closed
Tracked by #97
jimeh opened this issue Jan 15, 2024 · 2 comments
Closed
Tracked by #97

Switch to go-katapult@next in new Provider Framework implementation #121

jimeh opened this issue Jan 15, 2024 · 2 comments
Assignees

Comments

@jimeh
Copy link
Contributor

jimeh commented Jan 15, 2024

When krystal/go-katapult#150 is completed, there will be a new "next" version of the go-katapult client, that is generated from Katapult's OpenAPI schema.

We should try switching the new interval/v6provider package over to this new client. This will be the first real-world use of the new client, serving as a good way to evaluate it, and make adjustments to it if needed. While also slowly moving the Terraform provider codebase forward as well.

@jimehk
Copy link
Member

jimehk commented Jul 8, 2024

@ikadix Can this be closed now that #127 is merged?

@ikadix
Copy link
Collaborator

ikadix commented Jul 8, 2024

Yup happy for this to be closed

@jimeh jimeh closed this as completed Jul 8, 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

No branches or pull requests

3 participants