Tag the data-plane-api repository as part of the envoy release process

[jpeach]

Title: Tag the data-plane-api repository as part of the envoy release process

Description:

It it not very clear how to match the xDS API to the right version of Envoy. go-control-plane releases don't line up with Envoy releases, and consuming xDS protobufs directly from the Envoy repository means pulling a large repository and (I think) reimplementing a bunch of tooling.

I did experiment with generating the tags in the data-plane-api repository, but since only protobuf commits get mirrored, there's not enough git history to create all the corresponding tags. Probably solvable by not using bash, but just tagging as part of the envoy release seems more direct and simpler.

I'm happy to help with this if i can, but I expect this needs someone with permissions to tag repositories and a good understanding of the Envoy release machinery.

#! /usr/bin/env bash

set -o errexit

readonly ENVOYDIR=~/upstream/envoy

envoy::tags() {
    (
        cd "$ENVOYDIR"

        # Note that the sort works to order releases from newest to oldest as long
        # as Envoy never goes to v2, or to a 3-digit minor release.
        for release in $(git tag | egrep '^v[[:digit:]]([.][[:digit:]]+)+' | sort -t. -n -r -k 2,3); do
            printf "%s\t%s\n" "$release" "$(git rev-parse "$release")"
        done
    )
}

closest::release() {
    local sha="$1"

    (
        cd "$ENVOYDIR"
     
        git describe --tags "$sha" | grep -E --only-matching '^v[[:digit:]]([.][[:digit:]]+)+'
    )
}

mirror::history() {
    git log | awk '
    BEGIN {
        Count = 0
    }

    /^commit / {
        Commit[Count] = $2
    }

    /Mirrored from/ {
        Mirror[Count] = $5
        Count++
    }

    END {
        for (n = 0; n < Count; n++) {
            printf "%s\t%s\n", Commit[n], Mirror[n]
        }
    }
    '
}

declare -A releases

envoy::tags | while read tag sha ; do
    releases[$tag]=$sha
done

currentvers=

mirror::history | while read sha mirror ; do
    # closest vers tells us the last envoy version that was released
    # prior to this commit.
    closestvers=$(closest::release "$mirror")
    printf "%s\t%s\n" $sha $closestvers

    if [ -z "$currentvers" ]; then
        currentvers=$closestvers
    fi

    # At the version boundary, tag the new version.
    if [ "$currentvers" != "$closestvers" ]; then
        echo git tag "$currentvers" "$sha"
        currentvers=$closestvers
    fi
done

[jpeach]

xref envoyproxy/go-control-plane#391

[phlax]

cc @ggreenway @snowp

[alecholmez]

@jpeach and I also had an offline conversation about potentially moving the build of go-control-plane away from bazel since it adds quite a bit of complexity. We would reference the data-plane-api protos as the source of truth

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.