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

Use the upstream extracted Go SDK for XenOrchestra #174

Closed
wants to merge 3 commits into from

Conversation

ringods
Copy link
Contributor

@ringods ringods commented Nov 17, 2021

Fixes #173

The Go SDK for XenOrchestra has been extracted to https://github.com/vatesfr/xo-sdk-go. In this pull request, I change this TF provider to start using this extracted provider.

@ddelnano
Copy link
Collaborator

Thanks for opening this. I'm trying to prioritize getting #175 merged so I can release the provider (since it's been a while since the last release). That will require a minor change to the vatesfr/xo-sdk-go client. I'll follow up with that small change and run it against the provider's test suite tomorrow.

@ddelnano ddelnano mentioned this pull request Nov 19, 2021
1 task
@4censord
Copy link
Contributor

In #213 and #195 I did some minor changes to the client.
Should I open those as separate PRs against the extracted client SDK?

@ddelnano
Copy link
Collaborator

Sorry for the delay, but I'll be giving your PRs a look this week.

@ddelnano ddelnano closed this Oct 11, 2023
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.

Split Go client/SDK in a separate git repository?
3 participants