chore(codepipeline): remove the aws-codepipeline-api package

[skinny85]

Fixes #2157

---

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
• Title and Description
  • Change type: title prefixed with fix, feat 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.

[RomainMuller]

This needs to be turned into a deprecation notice instead..... Like we did for @aws-cdk/aws-sam in #2110, and only delete the package for the next release. Note that - you should set the deprecated attribute in package.json to the actual deprecation string instead of a boolean (that's a nifty, undocumented feature of npmjs :D).

[skinny85]

This package was effectively "deprecated" when #2098 was merged. I say "deprecated" in quotes, as I didn't know about this NPM feature, so I didn't set the deprecated attribute in package.json. However, I did remove all of the code from the package, and left it practically empty.

Since then, there was a release of the CDK with this empty shell version of this package, 0.28.0. Hence why we want to remove it now.

Are you OK with this @RomainMuller , or do you want to release this package one more time, in 0.29.0, in this empty shell version, just with the added deprecated attribute in package.json?

[skinny85]

@RomainMuller ping

[skinny85]

Rebased to solve the conflict.

[skinny85]

Removed the package.json which was resolved as an empty file in the conflict instead of being removed.