api: include v1alpha1 in proto_sync.py

[derekargueta]

Description: Follow-up to #8133, these likely escaped detection since they're versioned "v1alpha1" and the cloning script only searches for the last major version. This should be a one-off to get these caught up so I'm not modifying the tooling to accommodate these.
Risk Level: low
Testing: N/A
Docs Changes: N/A
Release Notes: N/A

Signed-off-by: Derek Argueta [email protected]

[repokitteh-read-only]

CC @envoyproxy/api-shepherds: Your approval is needed for changes made to api/.

🐱

Caused by: #9175 was opened by derekargueta.

see: more, trace.

[htuch]

@derekargueta I think we do need to have the tools do this, since these APIs might gain new fields before we do the v3 cut. I think it's fairly easy to do, check out tools/type_whisperer/typedb_gen.py and tools/proto_sync.py, look for references to v2alpha.

[derekargueta]

I didn't want to add one-off logic but since we already handling vNalphaN for v2 in tools/proto_sync.py I feel less bad :) will push an update.

[repokitteh-read-only]

CC @envoyproxy/api-shepherds: Your approval is needed for changes made to api/.

🐱

Caused by: #9175 was synchronize by derekargueta.

see: more, trace.

[derekargueta]

@htuch tooling updated. I believe it's is working as expected. When running with some debug prints, I verified it picks up the v1alpha1 bazel targets but hits this line because (IIUC) there are no deprecated fields in v1alpha1 for these two protos so there's nothing to modify.

[htuch]

@derekargueta ah yeah. So, I think your tool changes make sense, but then we shouldn't have the actual protos in v3alpha. We're only upgrading packages that have either had a breaking change or transitively depend on a package that has been upgraded. We basically have a DAG of versions.

[htuch]

Thanks!