Skip to content

Conversation

merzwilliam
Copy link
Contributor

Issue #, if available:
#1186

Description of changes:
Added KMSEncryptPolicy policy template following the similar KMSDecryptPolicy template and updated related tests.

Description of how you validated changes:
Validated via "make pr" command and checking transformed template.

Checklist:

  • Write/update tests
  • make pr passes
  • Update documentation
  • Verify transformed template deploys and application functions as expected
  • Add/update example to examples/2016-10-31

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

@codecov-io
Copy link

codecov-io commented Oct 10, 2019

Codecov Report

Merging #1192 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1192   +/-   ##
=======================================
  Coverage   94.36%   94.36%           
=======================================
  Files          71       71           
  Lines        3621     3621           
  Branches      713      713           
=======================================
  Hits         3417     3417           
  Misses        104      104           
  Partials      100      100

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5bd587c...eb23236. Read the comment docs.

@ShreyaGangishetty ShreyaGangishetty changed the base branch from master to develop October 11, 2019 17:05
@ShreyaGangishetty ShreyaGangishetty self-assigned this Oct 11, 2019
@jlhood jlhood force-pushed the feat/Add_KMSEncryptPolicy_policy_template branch from eb23236 to 6a1799b Compare October 15, 2019 16:45
Copy link
Contributor

@jlhood jlhood left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yay! Thanks for adding this! 😄I went ahead and fixed the merge conflict so this should be good to go!

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