Proposal for final CodePipeline Actions scheme: naming and code organization #424
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.
This PR contains what will (hopefully) be the final iteration of the way we structure our CodePipeline Actions.
The scheme is the following:
aws-codecommit-codepipeline
, the 2 CodeBuild Actions live inaws-codebuild-codepipeline
, etc.).Examples:
aws-codepipeline-aws-actions
, that has all of the CodePipeline integrations packages (aws-codecommit-codepipeline
,aws-codebuild-codepipeline
, etc.) as dependencies. It re-exports all of the Action under the namespace of the integration service. This is in oder to aid in discoverability, and make it easier for customers to just get all of the integrations with oneimport
.Examples:
Commits:
By submitting this pull request, I confirm that my contribution is made under
the terms of the beta license.