OpenSearch/rest-api-spec/test/cluster.put_settings/10_basic.yaml

---
setup:
  - skip:
      version:  "all"
      reason:  leaves transient metadata behind, need to fix it
---
"Test put settings":
  - do:
      cluster.put_settings:
        body:
          transient:
            discovery.zen.minimum_master_nodes: 1
        flat_settings: true

  - match: {transient: {discovery.zen.minimum_master_nodes: "1"}}

  - do:
      cluster.get_settings:
        flat_settings: true

  - match: {transient: {discovery.zen.minimum_master_nodes: "1"}}
Basic tests for get/set cluster settings 2013-07-18 16:46:41 +02:00			`---`
[TEST] Replaced RestTestSuiteRunner with parametrized test that uses RandomizedRunner directly ElasticsearchRestTests extends now ElasticsearchIntegrationTest and makes use of our ordinary test infrastructure, in particular all randomized aspects now come for free instead of having to maintain a separate (custom) tests runner We previously parsed only the tests that needed to be run given the version of the cluster the tests are running against. This doesn't happen anymore as it didn't buy much and it would be harder to support as the tests get now parsed before the test cluster gets started. Thus all the tests are now parsed regardless of their skip sections, afterwards the ones that don't need to be run will be skipped through assume directives. Fixed REST tests that rely on a specific number of shards as this change introduces also random number of shards and replicas (through randomIndexTemplate) Closes #5654 2014-03-10 13:48:17 +01:00			`setup:`
			`- skip:`
Tests: Add shortcut "all" to skip version ranges in rest tests This was suggested on #10656 as cleaner than " - " to indicate all versions should be skipped. closes #10702 2015-04-21 10:03:36 -07:00			`version: "all"`
[TEST] Replaced RestTestSuiteRunner with parametrized test that uses RandomizedRunner directly ElasticsearchRestTests extends now ElasticsearchIntegrationTest and makes use of our ordinary test infrastructure, in particular all randomized aspects now come for free instead of having to maintain a separate (custom) tests runner We previously parsed only the tests that needed to be run given the version of the cluster the tests are running against. This doesn't happen anymore as it didn't buy much and it would be harder to support as the tests get now parsed before the test cluster gets started. Thus all the tests are now parsed regardless of their skip sections, afterwards the ones that don't need to be run will be skipped through assume directives. Fixed REST tests that rely on a specific number of shards as this change introduces also random number of shards and replicas (through randomIndexTemplate) Closes #5654 2014-03-10 13:48:17 +01:00			`reason: leaves transient metadata behind, need to fix it`
			`---`
Basic tests for get/set cluster settings 2013-07-18 16:46:41 +02:00			`"Test put settings":`
			`- do:`
			`cluster.put_settings:`
			`body:`
			`transient:`
			`discovery.zen.minimum_master_nodes: 1`
Add support for flat_settings flag to all REST APIs that output settings Closes #4140 2014-01-06 11:50:57 -05:00			`flat_settings: true`
Basic tests for get/set cluster settings 2013-07-18 16:46:41 +02:00
			`- match: {transient: {discovery.zen.minimum_master_nodes: "1"}}`

			`- do:`
Add support for flat_settings flag to all REST APIs that output settings Closes #4140 2014-01-06 11:50:57 -05:00			`cluster.get_settings:`
			`flat_settings: true`
Basic tests for get/set cluster settings 2013-07-18 16:46:41 +02:00
			`- match: {transient: {discovery.zen.minimum_master_nodes: "1"}}`