envoyproxy/gateway

Rename extensionApis to extensionAPIs

Open

#5,764 opened on Apr 18, 2025

View on GitHub
 (2 comments) (0 reactions) (1 assignee)Go (802 forks)auto 404
help wanted

Repository metrics

Stars
 (2,871 stars)
PR merge metrics
 (Avg merge 14d 16h) (153 merged PRs in 30d)

Description

Description:

Describe the issue.

We've defined the field name as extensionApis https://github.com/envoyproxy/gateway/blob/6863a17a99eec2a46623fd8b275a2dae186223db/api/v1alpha1/envoygateway_types.go#L91

Instead it should be extensionAPIs based off https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#constants

We'll need to support this while maintaining backwards compatibility

[optional Relevant Links:]

Any extra documentation required to understand the issue.

Contributor guide

Research direction
Identify all usages of extensionApis field in the codebase, and implement a dual approach: keep extensionApis as a deprecated alias and add extensionAPIs as the new field. Ensure backward compatibility by handling both in serialization/deserialization.
Tech stack
go
Domain
backendapi
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoKubernetes API conventions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60