[float] [[breaking_70_plugins_changes]] === Plugins changes [float] ==== Azure Repository plugin * The legacy azure settings which where starting with `cloud.azure.storage.` prefix have been removed. This includes `account`, `key`, `default` and `timeout`. You need to use settings which are starting with `azure.client.` prefix instead. * Global timeout setting `cloud.azure.storage.timeout` has been removed. You must set it per azure client instead. Like `azure.client.default.timeout: 10s` for example. See {plugins}/repository-azure-repository-settings.html#repository-azure-repository-settings[Azure Repository settings]. [float] ==== Google Cloud Storage Repository plugin * The repository settings `application_name`, `connect_timeout` and `read_timeout` have been removed and must now be specified in the client settings instead. See {plugins}/repository-gcs-client.html#repository-gcs-client[Google Cloud Storage Client Settings]. [float] ==== S3 Repository Plugin * The plugin now uses the path style access pattern for all requests. In previous versions it was automatically determining whether to use virtual hosted style or path style access. [float] ==== Analysis Plugin changes * The misspelled helper method `requriesAnalysisSettings(AnalyzerProvider provider)` has been renamed to `requiresAnalysisSettings` [float] ==== File-based discovery plugin * This plugin has been removed since its functionality is now part of Elasticsearch and requires no plugin. The location of the hosts file has moved from `$ES_PATH_CONF/file-discovery/unicast_hosts.txt` to `$ES_PATH_CONF/unicast_hosts.txt`. See <> for further information. [float] ==== Security Extensions As a consequence of the <>, the `getRealmSettings` method has been removed from the `SecurityExtension` class, and the `settings` method on `RealmConfig` now returns the node's (global) settings. Custom security extensions should register their settings by implementing the standard `Plugin.getSettings` method, and can retrieve them from `RealmConfig.settings()` or using one of the `RealmConfig.getSetting` methods. Each realm setting should be defined as an `AffixSetting` as shown in the example below: [source,java] -------------------------------------------------- Setting.AffixSetting MY_SETTING = Setting.affixKeySetting( "xpack.security.authc.realms." + MY_REALM_TYPE + ".", "my_setting", key -> Setting.simpleString(key, properties) ); -------------------------------------------------- The `RealmSettings.simpleString` method can be used as a convenience for the above. [float] ==== Tribe node removed Tribe node functionality has been removed in favor of <>.