Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Updating mainline-1.x branch #337

Merged
merged 16 commits into from
Apr 28, 2021

Conversation

robin-aws
Copy link
Contributor

Backporting all changes that weren't specific to the master branch (implicitly tracking 2.x now) to the new mainline-1.x branch.

Description of changes:

Already created mainline-1.x from the existing release-1.7.x branch. Used git cherry-pick on all changes in master since v2.0.0, with the following tweaks:

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Check any applicable:

  • Were any files moved? Moving files changes their URL, which breaks all hyperlinks to the files.

farleyb-amazon and others added 16 commits April 27, 2021 09:54
* Various fixes/cleanup after release of 2.0

  - Update decrypt_oracle and test_vector_handlers to use new constructs
  - Update changelog with correct commit hashes
  - Update _ClientConfig docstring to include commitment_policy
  - Fix oracle CI
  - Update the release tox environments to reduce risk of releasing to the wrong repo
* chore: Update README section on using StrictAwsKmsKeyProvider

Be more explicit about the fact that, when using a
StrictAwsKmsMasterKeyProvider, key aliases are not
supported on decryption

* chore: remove test requirement dependency on old versions of attrs
Adding buildspec to batch build
multiple Python runtimes

* Python 2.7
* Python 3.5
* Python 3.6
* Python 3.7
* Python 3.8
Moving to CodeBuild for CI
This is a step towards a more continuous release process. If
this ends up being a productive path, we can expect to
pull more validation into these codebuild specs.
Otherwise it just pulls down "latest", and with eventual consistency on PyPi
we might end up pulling down a previous version and not actually validating
our release.

This has the downside that, again due to eventual consistency, the new
version might not show up yet causing the build to fail. Since this build
is idempotent this is not the end of the world, but we may want to make
this more robust in the future.
Now the test release validation does the same checks as the prod release
(running the sample application against the new version). To support this
I've also refactored out the validation steps into a dedicated spec so both
the prod and test specs can depend on it.
Address Issue aws#331 Typo in docstring for StreamDecryptor by correctly referring to the classes actions as decryption as compared to encryption.
…#335)

We had a copy/paste error and were pointing at the CLI
The policy set earlier doesn’t exist in the 1.x branch. and this value should be perfectly equivalent since the decrypt oracle only decrypts.
@robin-aws robin-aws merged commit 8e6b9e5 into aws:mainline-1.x Apr 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants