You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a nice document referencing how one could use kcp as a library. However, this document does not help users manage imports and is not tested against changes to kcp over time. I recently incorporated kcp into a larger project that depends on a number of k8s libraries, and finding the right mix of replace statements proved challenging, mostly due to some of the sequencing of rolling out logicalclusterv3 changes to the various kcp libraries.
Proposed Solution
It would be great if we set up a stand-alone repo that depended on kcp and was verified to work in CI. This would allow for folks looking to use kcp as a library to have a "known good" configuration to copy.
Alternative Solutions
An alternative option would be to build this example in kcp-dev/kcp, but that would result in relative path dependencies, which would not mirror the user experience of folks depending on the project.
Want to contribute?
I would like to work on this issue.
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Feature Description
There is a nice document referencing how one could use kcp as a library. However, this document does not help users manage imports and is not tested against changes to kcp over time. I recently incorporated kcp into a larger project that depends on a number of k8s libraries, and finding the right mix of
replace
statements proved challenging, mostly due to some of the sequencing of rolling outlogicalclusterv3
changes to the various kcp libraries.Proposed Solution
It would be great if we set up a stand-alone repo that depended on kcp and was verified to work in CI. This would allow for folks looking to use kcp as a library to have a "known good" configuration to copy.
Alternative Solutions
An alternative option would be to build this example in
kcp-dev/kcp
, but that would result in relative path dependencies, which would not mirror the user experience of folks depending on the project.Want to contribute?
Additional Context
No response
The text was updated successfully, but these errors were encountered: