Skip to content

docs(opensearch): add example for token based import#20915

Merged
mergify[bot] merged 4 commits intoaws:mainfrom
akleiber:main
Jul 5, 2022
Merged

docs(opensearch): add example for token based import#20915
mergify[bot] merged 4 commits intoaws:mainfrom
akleiber:main

Conversation

@akleiber
Copy link
Copy Markdown
Contributor

@akleiber akleiber commented Jun 29, 2022

Documentation for changes made in PR #15219 - issue #15188

Normally one would not put the domain endpoint as a static value in a CF stack.
A more realistic use case is to manage an opensearch domain from CF stack A and use it via CF stack B, C, D ...
Stack A would export the domainEndpoint and also domainArn - the other stacks can then import those values and import the domain.

This PR will add an example for the realistic scenario so people do not end up with errors like "Invalid URL" when a token endpoint is provided.


All Submissions:

Adding new Unconventional Dependencies:

  • This PR adds new unconventional dependencies following the process described here

New Features

  • Have you added the new feature to an integration test?
    • Did you use yarn integ to deploy the infrastructure and generate the snapshot (i.e. yarn integ without --dry-run)?

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

@gitpod-io
Copy link
Copy Markdown

gitpod-io bot commented Jun 29, 2022

@aws-cdk-automation aws-cdk-automation requested a review from a team June 29, 2022 13:34
@github-actions github-actions bot added the p2 label Jun 29, 2022
Add another example on how to import an existing domain with values from `Fn.importValue()`.

Normally one would not put the domain endpoint as a static value in a CF stack.
A more realistic use case is to manage an opensearch domain from CF stack A and use it via CF stack B, C, D ...
Stack A would export the domainEndpoint and also domainArn - the other stacks can then import those values and import the domain.

Documentation for changes made in #15219
kaizencc
kaizencc previously approved these changes Jul 1, 2022
Copy link
Copy Markdown
Contributor

@kaizencc kaizencc left a comment

Choose a reason for hiding this comment

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

Thanks for the new example, @akleiber! Made some minor edits but this looks great.

@mergify mergify bot dismissed kaizencc’s stale review July 1, 2022 13:36

Pull request has been modified.

@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Jul 5, 2022

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).

@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Jul 5, 2022

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-cdk-automation
Copy link
Copy Markdown
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
  • Commit ID: 5001880
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

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

@mergify mergify bot merged commit 27160c3 into aws:main Jul 5, 2022
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Jul 5, 2022

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).

daschaa pushed a commit to daschaa/aws-cdk that referenced this pull request Jul 9, 2022
Documentation for changes made in PR aws#15219 - issue aws#15188

Normally one would not put the domain endpoint as a static value in a CF stack.
A more realistic use case is to manage an opensearch domain from CF stack A and use it via CF stack B, C, D ...
Stack A would export the domainEndpoint and also domainArn - the other stacks can then import those values and import the domain.

This PR will add an example for the realistic scenario so people do not end up with errors like "Invalid URL" when a token endpoint is provided.



----

### All Submissions:

* [x] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md)

### Adding new Unconventional Dependencies:

* [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-new-unconventional-dependencies)

### New Features

* [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)?
	* [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)?

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants