Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes:
Because of the delays that we introduced that are blocking the release of keyrings[1], this reverts the keyring changes to unblock releases between now and the keyring release. Keyring work is now present over on the
keyring
branch.NOTE: This revert is messy in no small part because the
keyring
branch lived for so long without merging back intomaster
. One of the affects of this is that we completely changed how a lot of our CI worked in that branch, and that carried over intomaster
when we merged. This is why this "revert" PR retains the CI changes: both because the user experience of the new CI is much better and because our branch protection rules now require these 70+ checks and temporarily removing that requirement is non-trivial.[1] https://github.com/awslabs/aws-encryption-sdk-specification/milestone/1
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Check any applicable: