Skip to content

[V2] Fix dataproxy proto: add code bundle artifact type and fix field numbering#7220

Merged
pingsutw merged 3 commits intov2from
fix-devbox-dataproxy
Apr 16, 2026
Merged

[V2] Fix dataproxy proto: add code bundle artifact type and fix field numbering#7220
pingsutw merged 3 commits intov2from
fix-devbox-dataproxy

Conversation

@pingsutw
Copy link
Copy Markdown
Member

@pingsutw pingsutw commented Apr 16, 2026

Why are the changes needed?

The dataproxy proto needs two fixes:

  1. A new ARTIFACT_TYPE_CODE_BUNDLE enum value is needed to support downloading code bundles (tarballs) generated for actions.
  2. The CreateDownloadLinkResponse field numbering used a reserved field 3 with fields 1 and 2 marked as reserved, which is unnecessary. The field is renumbered to 1 for a cleaner proto definition.

What changes were proposed in this pull request?

  • Added ARTIFACT_TYPE_CODE_BUNDLE = 2 to the ArtifactType enum in dataproxy_service.proto
  • Removed the reserved 1, 2 declaration from CreateDownloadLinkResponse and changed pre_signed_urls from field number 3 to field number 1

How was this patch tested?

Proto definition change only — verified the proto file is valid.

  • All new and existing tests passed.
  • All commits are signed-off.
  • main
    • Flyte 2 #6583
      • [V2] Fix dataproxy proto: add code bundle artifact type and fix field numbering 👈

… numbering

Add ARTIFACT_TYPE_CODE_BUNDLE to support code bundle downloads and
fix CreateDownloadLinkResponse field numbering to use field 1 instead
of reserved field 3.

Signed-off-by: Kevin Su <pingsutw@apache.org>
@github-actions github-actions bot mentioned this pull request Apr 16, 2026
3 tasks
Signed-off-by: Kevin Su <pingsutw@apache.org>
Signed-off-by: Kevin Su <pingsutw@apache.org>
@pingsutw pingsutw self-assigned this Apr 16, 2026
@pingsutw pingsutw added this to the V2 GA milestone Apr 16, 2026
@pingsutw pingsutw merged commit 04a3c03 into v2 Apr 16, 2026
21 checks passed
@pingsutw pingsutw deleted the fix-devbox-dataproxy branch April 16, 2026 06:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants