Skip to content

Introduce pkg/sdk go.mod and VPCNetworkConfiguration function helpers - #68

Open
ihgann wants to merge 2 commits into
vmware-tanzu:masterfrom
ihgann:topic/ihgann/vpcsdk
Open

Introduce pkg/sdk go.mod and VPCNetworkConfiguration function helpers#68
ihgann wants to merge 2 commits into
vmware-tanzu:masterfrom
ihgann:topic/ihgann/vpcsdk

Conversation

@ihgann

@ihgann ihgann commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

This change introduces a new go.mod for pkg/sdk to keep it isolated from the root go.mod and introduces VPCNetworkConfiguration function helpers related to NamespaceNetworkConfiguration in pkg/sdk.

Testing Done: make lint test

This change introduces a new go.mod for pkg/sdk to keep it isolated from
the root go.mod and introduces VPCNetworkConfiguration function helpers
related to NamespaceNetworkConfiguration in pkg/sdk.

@yangna0420 yangna0420 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I need replied on this changes on my VPC get

@lxiaopei lxiaopei left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Comment thread pkg/sdk/go.mod
require (
github.com/stretchr/testify v1.11.1
github.com/vmware-tanzu/net-operator-api v0.0.0
github.com/vmware-tanzu/nsx-operator/pkg/apis v0.0.0-20260818083459-96cb17ddc8e0

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Ian,Just curious about one question, github.com/vmware-tanzu/nsx-operator v0.0.0-20260604071952-21b82cc9119b this version is commonly used in our tera component, If the version v0.0.0-20260818083459-96cb17ddc8e0 is used now, will there be any risks? Do we need to keep all versions of tera side consistent?

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In fact, in my PR https://github-vcf.devops.broadcom.net/vcf/tera/pull/102721, I found that when the version changes, there are indeed some UT failures, so we need to make changes.

If decide use the new version. We might need to upgrade all the nsx-operator versions in tera together and do some UT fixes. However, that should be a separate PR. I don't want to introduce it into my PR

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Ian,Just curious about one question, github.com/vmware-tanzu/nsx-operator v0.0.0-20260604071952-21b82cc9119b this version is commonly used in our tera component, If the version v0.0.0-20260818083459-96cb17ddc8e0 is used now, will there be any risks? Do we need to keep all versions of tera side consistent?

This is an APIs sub-component. It would be good to keep consistent, yes, but this is not a dangerous pull as it's just API types.

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.

3 participants