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

chore: forward merge 'master' into 'v2-main' #13414

Merged
merged 105 commits into from
Mar 5, 2021
Merged

Conversation

aws-cdk-automation
Copy link
Collaborator

@aws-cdk-automation aws-cdk-automation commented Mar 5, 2021

Automated action from aws/cdk-ops

ericzbeard and others added 30 commits May 26, 2020 09:40
aws-cdk-automation and others added 9 commits March 4, 2021 10:42
Ran npm-check-updates and yarn upgrade to keep the `yarn.lock` file up-to-date.
I believe the reason our auto-approve workflow does not work is because it was triggered when the pull request was _created_ and before the `pr/auto-approve` label was applied to it.

This adds `types: [ labeled ]` so the workflow is triggered when a PR is labeled. The condition remains the same.
Some tricks we are using to locate packages on disk don't work
anymore under newer Node versions. Switch strategies.


----

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

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
This is a re-submit of the PR #12700,
which had to be reverted because of JSII issue aws/jsii#2256.
Since that issue has been fixed in JSII version `1.23.0`,
which is what we currently use,
re-introduce the changes from that PR.

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Use lerna to generate a topologically sorted list of `.tgz` files.

This list will be used during publishing to impose an order
on the package publishing actions.

Fixes #13221.


----

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

`allowAllTraffic` only applies to inbound traffic, but it should also apply to outbound traffic. 

Deprecate it and add a new enum-based property, `defaultAllowedTraffic`, which also allows controlling outbound traffic rules. There is no option to allow inbound but not outbound because there is no use case for that.

Fix #12673

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…overy records (#12798)

Adds `container` and `containerPort` as optional properties of `CloudMapOptions`. This change allows the user to select which container and container port the `SRV` record points to.

Closes #12796

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Bumps [actions/setup-node](https://github.com/actions/setup-node) from v2.1.4 to v2.1.5.
- [Release notes](https://github.com/actions/setup-node/releases)
- [Commits](actions/setup-node@v2.1.4...46071b5)

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Adam Ruka <adamruka@amazon.com>
@aws-cdk-automation aws-cdk-automation added pr/auto-approve Notifies the GH action to auto-approve this PR pr/forward-merge PR label to indicate forward merges of master to v2-main pr/no-squash This PR should be merged instead of squash-merging it labels Mar 5, 2021
@gitpod-io
Copy link

gitpod-io bot commented Mar 5, 2021

@mergify
Copy link
Contributor

mergify bot commented Mar 5, 2021

Thank you for contributing! Your pull request will be automatically updated and merged without squashing (do not update manually, and be sure to allow changes to be pushed to your fork).

@aws-cdk-automation
Copy link
Collaborator Author

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject89A8053A-LhjRyN9kxr8o
  • Commit ID: 28e2dde
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

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

@skinny85 skinny85 merged commit 94c1750 into v2-main Mar 5, 2021
@skinny85 skinny85 deleted the v2/forward-merge-20210305 branch March 5, 2021 21:45
@njlynch njlynch restored the v2/forward-merge-20210305 branch March 22, 2021 16:02
@njlynch njlynch deleted the v2/forward-merge-20210305 branch March 22, 2021 16:33
@njlynch njlynch restored the v2/forward-merge-20210305 branch March 22, 2021 17:18
njlynch added a commit that referenced this pull request Mar 23, 2021
The forward merge #13414 was erroneously squash-merged, resulting in some
defects in the future forward merges. In particular, #13426 was dropped,
un-reverting the commit and causing issues. There were also some test changes
from #13462 that appeared to be dropped.

This PR fixes the issue by just directly applying a patch to v2-main that solves
the difference between the current v2-main and what we'd have if we un-squashed
the squashed merge-commit and replayed all commits after that.

This is an effective duplicate of #13742, except that this is a clean patch that
can be applied, whereas the other is a rebased branch that will need to be
force-pushed to be applied.
@njlynch njlynch deleted the v2/forward-merge-20210305 branch March 25, 2021 17:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/auto-approve Notifies the GH action to auto-approve this PR pr/forward-merge PR label to indicate forward merges of master to v2-main pr/no-squash This PR should be merged instead of squash-merging it
Projects
None yet
Development

Successfully merging this pull request may close these issues.