aws / aws/eks-anywhere

Reconcile govmomi / govc Dependencies

Open
#2,853 0 comments 0 reactions 0 assignees View on GitHub
area/cli kind/cleanup team/cli
Dominant language
Go
Stars
2.1k
Forks
328
Avg merge
1d 4h
Merged PRs (30d)
9

Description

With the implementation of #2744 EKS-A now depends on both govmomi and govc, a CLI tool derived from the govmomi vSphere client.

We should reconcile these dependencies so we only rely on one.

One option is to convert all our govc calls to govmomi calls.

Another is to open a PR in to the [govmomi project](https://github.com/vmware/govmomi) and add the functionality we need to the govc CLI.

Contributor guide

Open the contributing guide

Research direction

No files or tests are named. Start by reviewing the implementation of #2744 and inventorying EKS-A's govmomi and govc usage; compare converting govc calls with adding the needed functionality upstream. Done means EKS-A relies on one dependency while retaining the required functionality.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
infrastructure, tooling
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.