Circular dependency between the kpt module and krm-functions-sdk module

[liamfallon]

The kpt module is dependent on the krm-functions-sdk module:

kpt/go.mod

Line 14 in c3305fe

github.com/kptdev/krm-functions-sdk/go/fn v1.0.2

The krm-functions-sdk go module is dependent on the kpt module:
https://github.com/kptdev/krm-functions-sdk/blob/b371169de8a9ce627db9a7d140aad3eddb68af62/go/fn/go.mod#L8

This circular dependency should be removed.

[Jaisheesh-2006]

Hi @liamfallon, I would like to take this issue up and resolve the circular dependency.

Proposed Approach

1. Dependency Audit: I will identify the specific packages and structs in krm-functions-sdk that are importing kpt.
2. Refactor: Depending on the exact intersection, I will break the cycle by either extracting the shared types into a neutral, foundational package, or by defining interfaces within the SDK to implement dependency inversion.
3. Module Cleanup: I will update the import paths across both repositories and run go mod tidy to ensure the module requirements are completely decoupled.

Please assign this to me. Let me know if the maintainer team has a strict preference between extracting a shared package versus using interface injection for this specific SDK boundary.

[SurbhiAgarwal1]

Hi @liamfallon, I'm interested in working on this issue .