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

task: Move python sdk into its own repository #4232

Closed
dgarros opened this issue Sep 1, 2024 · 0 comments
Closed

task: Move python sdk into its own repository #4232

dgarros opened this issue Sep 1, 2024 · 0 comments
Labels
type/task Body of work related to an epic

Comments

@dgarros
Copy link
Collaborator

dgarros commented Sep 1, 2024

Component

Python SDK

Task Description

Currently the python SDK lives in the same Git repository as Infrahub under the directory python_sdk. The question of moving it into its own repository keeps coming back so I thought having a place to centralize the discussion would be useful.

Like everything in tech, it's a tradeoff
In my perspective here are the pros and cons of having both libraries in the same repository

Pro

  • Easier to implement a feature or fix an issue that affects both Infrahub and the Python SDK
  • Easier to do end to end testing and identify issues early

Cons

  • Difficult to have a different release cycle between Infrahub and the SDK since we are sharing the same branches develop, stable.
  • Probably harder for people outside of OpsMill to follow what is going on with the SDK or contribute to it because there is a lot of activity on the project
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/task Body of work related to an epic
Projects
None yet
Development

No branches or pull requests

1 participant