OpenSearch/plugins/jvm-example/rest-api-spec/test/jvm_example/10_basic.yaml

# Integration tests for JVM Example Plugin
#
"JVM Example loaded":
    - do:
        cluster.state: {}

    # Get master node id
    - set: { master_node: master }

    - do:
        nodes.info: {}

    - match:  { nodes.$master.plugins.0.name: jvm-example  }
    - match:  { nodes.$master.plugins.0.jvm: true  }
This method on settings loaded a class, based on a setting value, using the default classloader. It had all kinds of leniency in how the classname was found, and simply cannot work with plugins having isolated classloaders. This change removes that method. Some of the uses of it were for custom extension points, like custom repository or discovery types. A lot were just there to plugin mock implementations for tests. For the settings that were legitimate, all now support plugins adding the given setting via onModule. For those that were specific to tests for mocks, they now use Classes.loadClass (a helper around Class.forName). This is a temporary measure until (in a future PR) tests can change the implementation via package private statics. I also removed a number of unnecessary intermediate modules, added a "jvm-example" plugin that can be filled in in the future as a smoke test for breaking plugins, and gave some documentation to "spawn" modules interface. closes #12643 closes #12656 2015-08-10 14:04:45 -07:00			`# Integration tests for JVM Example Plugin`
			`#`
			`"JVM Example loaded":`
			`- do:`
			`cluster.state: {}`

			`# Get master node id`
			`- set: { master_node: master }`

			`- do:`
			`nodes.info: {}`

			`- match: { nodes.$master.plugins.0.name: jvm-example }`
			`- match: { nodes.$master.plugins.0.jvm: true }`