Andrew Harding

We released 2.1.1 yesterday. You should hopefully to good to go! Let me know if there is anything else I can help with.

Hi @vudh1. I didn't discover this by having a problem firsthand. Rather, I was looking through the SDK code when we migrated to v2 to make double check some usage...

Great questions @boyanguber! > When this becomes enforced in 1.4, does that mean that old agent ID's that don't conform to the new convention will not be able to attest/sync...

So the maintainers huddled on this. I think this is the plan of action we'd like to follow: 1. Warn on the undesired ID usage (this is [already merged](#2694) and...

This should be an easy fix. We should audit all of the built-in plugins that do the TOFU checks to ensure the ID is included in the error.

Sorting on `EntryId` was a quick band-aid to get consistent results between two successive results streamed off the Workload API (it was random before that). It was not intended to...

We discussed this issue at length today. The consensus was to keep the issues of consistent ordering (this issue) and administrative control (#744) separate. For administrative control, we think that...

I brought this up with SIG-SPEC and was reminded of a discussion we had while drafting the endpoint specification: > We generally assume that the ability to have a server...

Of course, if we support SPIFFE bundle content at the URL, we could presumably also support loading a SPIFFE bundle from disk, so maybe the configurable should just be ```...

Deprecating the old config might have implications for current bundle notifiers, which push up the PEM-encoded X.509 authority material from the bundles.