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

feat(s3-deployment): allow multiple Sources for single Deployment #4105

Merged
merged 4 commits into from
Sep 19, 2019

Conversation

CaerusKaru
Copy link
Contributor

In some cases, a user may want to inject other sources into a
deployment. For instance, storing JavaScript bundles in one
directory and images in another, then combining them in a
single bucket for CloudFront distributions.

  • All sources will be fetched and consolidated into one directory
    before being zipped as normal prior to deployment

BREAKING CHANGE:

  • Property source is now sources and is a Source array

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

@mergify
Copy link
Contributor

mergify bot commented Sep 16, 2019

Thanks so much for taking the time to contribute to the AWS CDK ❤️

We will shortly assign someone to review this pull request and help get it
merged. In the meantime, please take a minute to make sure you follow this
checklist
:

  • PR title type(scope): text
    • type: fix, feat, refactor go into CHANGELOG, chore is hidden
    • scope: name of module without aws- or cdk- prefix or postfix (e.g. s3 instead of aws-s3-deployment)
    • text: use all lower-case, do not end with a period, do not include issue refs
  • PR 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>
  • Testing
    • Unit test added. Prefer to add a new test rather than modify existing tests
    • CLI or init templates change? Re-run/add CLI integration tests
  • Documentation
    • README: update module README to describe new features
    • API docs: public APIs must be documented. Copy from official AWS docs when possible
    • Design: for significant features, follow design process

@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Copy link
Contributor

@eladb eladb left a comment

Choose a reason for hiding this comment

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

Looks very good! See some comments.

@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • Result: FAILED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@CaerusKaru CaerusKaru force-pushed the adam/s3-mult branch 2 times, most recently from 56e8691 to 229154f Compare September 18, 2019 18:39
@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • Result: FAILED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

eladb
eladb previously requested changes Sep 19, 2019
packages/@aws-cdk/aws-s3-deployment/lib/source.ts Outdated Show resolved Hide resolved
Adam Plumer added 4 commits September 19, 2019 10:48
In some cases, a user may want to inject other sources into a
deployment. For instance, storing JavaScript bundles in one
directory and images in another, then combining them in a
single bucket for CloudFront distributions.

* All sources will be fetched and consolidated into one directory
  before being zipped as normal prior to deployment

BREAKING CHANGE:
* Property `source` is now `sources` and is a `Source` array
@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@mergify
Copy link
Contributor

mergify bot commented Sep 19, 2019

Thank you for contributing! Your pull request is now being automatically merged.

@mergify mergify bot merged commit 2ce4a87 into aws:master Sep 19, 2019
@CaerusKaru CaerusKaru deleted the adam/s3-mult branch September 19, 2019 17:47
eladb pushed a commit that referenced this pull request Sep 23, 2019
)

* feat(s3-deployment): allow multiple Sources for single Deployment

In some cases, a user may want to inject other sources into a
deployment. For instance, storing JavaScript bundles in one
directory and images in another, then combining them in a
single bucket for CloudFront distributions.

* All sources will be fetched and consolidated into one directory
  before being zipped as normal prior to deployment

BREAKING CHANGE:
* Property `source` is now `sources` and is a `Source` array

* fixup! feat(s3-deployment): allow multiple Sources for single Deployment

* fixup! feat(s3-deployment): allow multiple Sources for single Deployment

* fixup! feat(s3-deployment): allow multiple Sources for single Deployment
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.

None yet

3 participants