Push versioned Envoy API artifacts to a public maven repository?

Open
#262 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
build-system, release

Research direction

No files or tests are named. Start by comparing the proto-pull and build-artifacts steps in transferwise/envoy-api-java with java-control-plane's current build and release setup. Done would require an agreed approach for publishing versioned generated proto artifacts publicly so consumers can use a canonical version.

Written by the indexing model from the issue text.

Description

Hello,

In https://github.com/transferwise/envoy-api-java we replicate the proto-pull + build-artifacts steps from this repo. But it would be nicer if java-control-plane could push the generated proto artifacts, so we could use the canonical version (and avoid duplicating work).

What do you think?

Dominant language
Java
Stars
312
Forks
150
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from envoyproxy/java-control-plane

All issues in envoyproxy/java-control-plane

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.