We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
opensearch_snapshot_repository
During the migration of an OpenSearch cluster, preventing write operations on the destination OpenSearch can avoid accidents.
I hope readonly flag in opensearch_snapshot_repository resource like below.
# Create a snapshot repository resource "opensearch_snapshot_repository" "repo" { name = "es-index-backups" type = "s3" settings = { bucket = "es-index-backups" region = "us-east-1" role_arn = "arn:aws:iam::123456789012:role/MyRole" readonly = true } }
A clear and concise description of any alternative solutions or features you've considered.
The text was updated successfully, but these errors were encountered:
[Triage] Hey @shmokmt I assume you are looking for the following when readonly = true is added
readonly = true
"index_settings": { "index.blocks.read_only": false },
This snapshot feature was added from PR #125, can you please take a look and see if you can contribute ?
Thanks Adding @duboisph @rblcoder @bbarani
Sorry, something went wrong.
This request is regarding the opensearch_snapshot_repository registering, not Snapshot Management feature added in #125.
That said, looking at the opensearch_snapshot_repository code, this should already work out of the box. The settings map is passed completely to the API.
settings
You can use all settings as allowed by the API, docs: https://opensearch.org/docs/latest/api-reference/snapshots/create-repository/
@shmokmt Have you tried this and isn't it working?
I'm sorry. It seems it was my misunderstanding. It worked fine. thanks!
No branches or pull requests
Is your feature request related to a problem?
During the migration of an OpenSearch cluster, preventing write operations on the destination OpenSearch can avoid accidents.
What solution would you like?
I hope readonly flag in
opensearch_snapshot_repository
resource like below.What alternatives have you considered?
A clear and concise description of any alternative solutions or features you've considered.
Do you have any additional context?
The text was updated successfully, but these errors were encountered: