-
Notifications
You must be signed in to change notification settings - Fork 4k
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(elasticsearch): remove elasticsearch legacy reference #23943
Conversation
Elastic has followed up with a request that we remove "legacy Elasticsearch" references from our docs for legal reasons. They supplied these two links to remove the string from: https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_elasticsearch-readme.html https://docs.aws.amazon.com/cdk/api/v1/docs/aws-elasticsearch-readme.html This PR is for v1 (the second link). Does updating v1 automatically update v2? Closes https://t.corp.amazon.com/V825034754.
@chatnish FYI in these cases we usually make the PR for v2 (which this one is) and after it's merged we use some automation to backport the change to v1. I will take care of that. |
@Mergifyio backport v1-main |
✅ Backports have been created
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Elastic has followed up with a request that we remove "legacy Elasticsearch" references from our docs for legal reasons. They supplied these two links to remove the string from: https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_elasticsearch-readme.html and https://docs.aws.amazon.com/cdk/api/v1/docs/aws-elasticsearch-readme.html Internal reference: V825034754. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license* (cherry picked from commit 0a4ad38)
…23943) (#23949) This is an automatic backport of pull request #23943 done by [Mergify](https://mergify.com). --- <details> <summary>Mergify commands and options</summary> <br /> More conditions and actions can be found in the [documentation](https://docs.mergify.com/). You can also trigger Mergify actions by commenting on this pull request: - `@Mergifyio refresh` will re-evaluate the rules - `@Mergifyio rebase` will rebase this PR on its base branch - `@Mergifyio update` will merge the base branch into this PR - `@Mergifyio backport <destination>` will backport this PR on `<destination>` branch Additionally, on Mergify [dashboard](https://dashboard.mergify.com/) you can: - look at your merge queues - generate the Mergify configuration with the config editor. Finally, you can contact us on https://mergify.com </details>
Elastic has followed up with a request that we remove "legacy Elasticsearch" references from our docs for legal reasons.
They supplied these two links to remove the string from: https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_elasticsearch-readme.html and https://docs.aws.amazon.com/cdk/api/v1/docs/aws-elasticsearch-readme.html
Internal reference: V825034754.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license