-
Notifications
You must be signed in to change notification settings - Fork 17
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
Upgrade to the microgrid API v0.16 #844
Comments
The current dependency problem is:
In the near future we need to make API common stable already to not end up in this situation again, so any breaking changes should go to v2. So we can also call the common API version v1.x.x already. We prioritized the update of the microgrid API in the SDK because we need to break this dependency conflict, but another solution is to extract the |
Since this update involves a lot of code changes, and now we have the https://github.com/frequenz-floss/frequenz-client-common-python/ that we'll need to use too, and we'll need to extract the microgrid API client to its own repo, we will do this update directly in the new repo. Then we update the SDK to remove the client and depend on the new repo, and update the high-level interface to use the new client. |
Blocked by: After we have the new microgrid API client repo with v0.16, we can update the internal usage of the client in the SDK. |
The upgrade to frequenz-api-microgrid >=0.16.0 needs a lot of changes in the code. We are not ready to do that yet, so we should ignore this dependency for now. See: frequenz-floss#844 Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
The upgrade to frequenz-api-microgrid >=0.16.0 needs a lot of changes in the code. We are not ready to do that yet, so we should ignore this dependency for now. See: * #844
What's needed?
We need to move development of many APIs forward, but new APIs depend on the common API v0.5, while the SDK is using the microgrid API v0.15, which depends on the common API v0.3, so actors for the new APIs can't be developed due to the API versions incompatibilities.
Proposed solution
Upgrade to the microgrid API v0.17.
Use cases
No response
Alternatives and workarounds
Copy the needed files in the common API to the new API repos. We are doing this in a couple of places, but it is starting to get messy.
Additional context
No response
The text was updated successfully, but these errors were encountered: