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

Setup a nightly integration workflow with a AWS Opensearch instance #18252

Open
megglos opened this issue May 6, 2024 · 0 comments
Open

Setup a nightly integration workflow with a AWS Opensearch instance #18252

megglos opened this issue May 6, 2024 · 0 comments
Labels
component/zeebe Related to the Zeebe component/team kind/toil Categorizes an issue or PR as general maintenance, i.e. cleanup, refactoring, etc. version:8.4.7 Marks an issue as being completely or in parts released in 8.4.7 version:8.5.1 Marks an issue as being completely or in parts released in 8.5.1 version:8.6.0-alpha1 Label that represents issues released on verions 8.6.0-alpha1

Comments

@megglos
Copy link
Contributor

megglos commented May 6, 2024

Description
Issues like #18251 revealed that ITs with a bare local opensearch instance are not enough for us to be sure the opensearch exporter works correctly with the AWS Opensearch service.

While it's not practical to include a real AWS opensearch service into our ITs, we should consider creating at least a nightly integration job that verifies compatibility.

@megglos megglos added kind/toil Categorizes an issue or PR as general maintenance, i.e. cleanup, refactoring, etc. component/zeebe Related to the Zeebe component/team labels May 6, 2024
@megglos megglos changed the title Setup a nightly integration pipeline with a AWS Opensearch instance Setup a nightly integration workflow with a AWS Opensearch instance May 6, 2024
github-merge-queue bot pushed a commit that referenced this issue May 6, 2024
## Description

While the bare opensearch service allows a missing leading slash, the
AWS service or it's ingress doesn't, returning a 400.

As I don't see an easy way to cover this in our ITs we may consider
following up with a nightly IT on prepared AWS Opensearch instance see
#18252 .

## Related issues

closes #18251
github-merge-queue bot pushed a commit that referenced this issue May 6, 2024
…18274)

# Description
Backport of #18253 to `stable/8.4`.

relates to #18252 #18251
original author: @megglos
github-merge-queue bot pushed a commit that referenced this issue May 6, 2024
…18275)

# Description
Backport of #18253 to `stable/8.5`.

relates to #18252 #18251
original author: @megglos
megglos added a commit that referenced this issue May 6, 2024
…endpoints (#18276)

# Description
Backport of #18253 to `release-8.6.0-alpha1`.

relates to #18252 #18251
original author: @megglos
@Zelldon Zelldon added version:8.4.7 Marks an issue as being completely or in parts released in 8.4.7 version:8.5.1 Marks an issue as being completely or in parts released in 8.5.1 version:8.6.0-alpha1 version:8.6.0-alpha1 Label that represents issues released on verions 8.6.0-alpha1 and removed version:8.6.0-alpha1 labels May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/zeebe Related to the Zeebe component/team kind/toil Categorizes an issue or PR as general maintenance, i.e. cleanup, refactoring, etc. version:8.4.7 Marks an issue as being completely or in parts released in 8.4.7 version:8.5.1 Marks an issue as being completely or in parts released in 8.5.1 version:8.6.0-alpha1 Label that represents issues released on verions 8.6.0-alpha1
Projects
None yet
Development

No branches or pull requests

2 participants