aws / aws/eks-anywhere

Generic Git Provider: deprecation path for GitOpsConfig

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

Description

What do we need to do to deprecate the `GitOpsConfig`?

Make a plan for what will need to be removed from the code base when we deprecate GitOpsConfig fully.

Add `//Deprecated` godocs to the `GitOpsConfig` struct and find other places where it would be worth-while to surface deprecation warnings to useres.

Contributor guide

Open the contributing guide

Research direction

Search the codebase for the GitOpsConfig struct and its other uses. Review how GitOpsConfig is exposed to users, then document the removals needed for full deprecation and add the requested //Deprecated Go documentation and any justified deprecation warnings. Done means the deprecation plan is recorded and the relevant user-facing surfaces are identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
devops
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.