fix(codepipeline): set correct prop names for KMS key

[CaerusKaru]

It seems like this might actually be a bug in the serialization
generator, since the return object doesn't require this to generate
the correct Cfn syntax

Not sure where to look for that though. In the meantime, this fixes
the issue where Cfn will spit out an error for Encountered unsupported property type

---

Pull Request Checklist

• Testing
  • Unit test added (prefer not to modify an existing test, otherwise, it's probably a breaking change)
  • CLI change?: coordinate update of integration tests with team
  • cdk-init template change?: coordinated update of integration tests with team
• Docs
  • jsdocs: All public APIs documented
  • README: README and/or documentation topic updated
  • Design: For significant features, design document added to design folder
• Title and Description
  • Change type: title prefixed with fix, feat and module name in parens, which will appear in changelog
  • Title: use lower-case and doesn't end with a period
  • Breaking?: last paragraph: "BREAKING CHANGE: <describe what changed + link for details>"
  • Issues: Indicate issues fixed via: "Fixes #xxx" or "Closes #xxx"
• Sensitive Modules (requires 2 PR approvers)
  • IAM Policy Document (in @aws-cdk/aws-iam)
  • EC2 Security Groups and ACLs (in @aws-cdk/aws-ec2)
  • Grant APIs (only if not based on official documentation with a reference)

---

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

[skinny85]

Thanks for the contribution @CaerusKaru , but this is not the correct solution. See the CI error:

@aws-cdk/aws-codepipeline: lib/pipeline.ts:535:9 - error TS2322: Type '{ Type: string; Id: string; }' is not assignable to type 'EncryptionKeyProperty'.
@aws-cdk/aws-codepipeline:   Object literal may only specify known properties, but 'Type' does not exist in type 'EncryptionKeyProperty'. Did you mean to write 'type'?
@aws-cdk/aws-codepipeline: 535         Type: 'KMS',
@aws-cdk/aws-codepipeline:             ~~~~~~~~~~~

[CaerusKaru]

@skinny85 Can you advise on the correct solution? There is clearly a bug, but I genuinely think that it's in the serialization, and not here (as CI clearly shows).

[rix0rrr]

Please wait until #2576 has been applied and see if the error still persists.

[eladb]

Any updates on this?

[skinny85]

I'm going to close this, as #3694 addresses the issue this PR was opened for.

[mergify]

Pull Request Checklist

• Testing

• Unit test added (prefer to add a new test rather than modify existing tests)
• CLI change? Re-run/add CLI integration tests

• Documentation

• Inline docs: make sure all public APIs are documented (copy & paste from official AWS docs)
• README: update module README
• Design: for significant features, follow the design process

• Title uses the format type(scope): text

• Type: fix, feat, refactor go into CHANGELOG, chore is hidden
• Scope: name of the module without the aws- or cdk- prefix or postfix (e.g. s3 instead of aws-s3-deployment)
• Style: use all lower-case, do not end with a period

• Description

• Rationale: describe rationale of change and approach taken
• Issues: Indicate issues fixed via: fixes #xxx or closes #xxx
• Breaking?: last paragraph: BREAKING CHANGE: <describe what changed + link for details>

• Sensitive Modules (requires 2 PR approvers)

• IAM document library (in @aws-cdk/aws-iam)
• EC2 security groups and ACLs (in @aws-cdk/aws-ec2)
• Grant APIs (if not based on official documentation with a reference)

[mergify]

Codebuild (Continuous Integration) build failed for current commits. Please check log and resolve before PR is merged.

[mergify]

Title does not follow the guidelines of Conventional Commits. Please adjust title before merge.