-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Add end-to-end test for reloading S3 credentials #116762
Merged
DaveCTurner
merged 3 commits into
elastic:main
from
DaveCTurner:2024/11/13/s3-reload-credentials-java-rest-test
Nov 14, 2024
Merged
Add end-to-end test for reloading S3 credentials #116762
DaveCTurner
merged 3 commits into
elastic:main
from
DaveCTurner:2024/11/13/s3-reload-credentials-java-rest-test
Nov 14, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We don't seem to have a test that completely verifies that a S3 repository can reload credentials from an updated keystore. This commit adds such a test.
DaveCTurner
added
>test
Issues or PRs that are addressing/adding tests
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
v9.0.0
v8.17.0
labels
Nov 13, 2024
Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination) |
elasticsearchmachine
added
the
Team:Distributed Coordination
Meta label for Distributed Coordination team
label
Nov 13, 2024
idegtiarenko
approved these changes
Nov 14, 2024
DaveCTurner
deleted the
2024/11/13/s3-reload-credentials-java-rest-test
branch
November 14, 2024 08:28
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this pull request
Nov 14, 2024
Similar to elastic#116762 but demonstrating that searchable snapshots pick up reloaded credentials too.
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this pull request
Nov 14, 2024
We don't seem to have a test that completely verifies that a S3 repository can reload credentials from an updated keystore. This commit adds such a test. Backport of elastic#116762 to 8.x.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Nov 14, 2024
We don't seem to have a test that completely verifies that a S3 repository can reload credentials from an updated keystore. This commit adds such a test. Backport of #116762 to 8.x.
Also backporting this to 8.16 since the tests for #116987 depend on it. |
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this pull request
Nov 18, 2024
We don't seem to have a test that completely verifies that a S3 repository can reload credentials from an updated keystore. This commit adds such a test. Backport of elastic#116762 to 8.16.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Nov 18, 2024
We don't seem to have a test that completely verifies that a S3 repository can reload credentials from an updated keystore. This commit adds such a test. Backport of #116762 to 8.16.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Nov 19, 2024
* Split searchable snapshot into multiple repo operations Each operation on a snapshot repository uses the same `Repository`, `BlobStore`, etc. instances throughout, in order to avoid the complexity arising from handling metadata updates that occur while an operation is running. Today we model the entire lifetime of a searchable snapshot shard as a single repository operation since there should be no metadata updates that matter in this context (other than those that are handled dynamically via other mechanisms) and some metadata updates might be positively harmful to a searchable snapshot shard. It turns out that there are some undocumented legacy settings which _do_ matter to searchable snapshots, and which are still in use, so with this commit we move to a finer-grained model of repository operations within a searchable snapshot. Backport of #116918 to 8.16 * Add end-to-end test for reloading S3 credentials We don't seem to have a test that completely verifies that a S3 repository can reload credentials from an updated keystore. This commit adds such a test. Backport of #116762 to 8.16.
alexey-ivanov-es
pushed a commit
to alexey-ivanov-es/elasticsearch
that referenced
this pull request
Nov 28, 2024
We don't seem to have a test that completely verifies that a S3 repository can reload credentials from an updated keystore. This commit adds such a test.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Distributed Coordination/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
Team:Distributed Coordination
Meta label for Distributed Coordination team
>test
Issues or PRs that are addressing/adding tests
v8.16.1
v8.17.0
v9.0.0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We don't seem to have a test that completely verifies that a S3
repository can reload credentials from an updated keystore. This commit
adds such a test.