honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Docs: Fix deprecation notices and typo to build docs 

Original commit: elastic/x-pack-elasticsearch@6e5504efd9
This commit is contained in:
Alexander Reelsen 2018-03-26 14:25:42 +02:00
parent 3a75435980
commit c2764cef98
4 changed files with 4 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/en/watcher/actions/hipchat.asciidoc
View File

@ -165,9 +165,7 @@ If you configure multiple HipChat accounts, you either need to set a default
HipChat account or specify which account the notification should be sent with
in the <<actions-hipchat, hipchat>> action.
deprecated[Storing the `auth_token` in the configuration file or using via updating the
settings now is deprecated, as you should use the keystore for this, see
<<secure-settings,secure settings>>]
deprecated[Storing the `auth_token` in the configuration file or using via updating the settings now is deprecated, as you should use the keystore for this, see <<secure-settings,secure settings>>]
[source,yaml]
--------------------------------------------------

3
docs/en/watcher/actions/jira.asciidoc
View File

@ -115,8 +115,7 @@ bin/elasticsearch-keystore xpack.notification.jira.account.monitoring.secure_use
bin/elasticsearch-keystore xpack.notification.jira.account.monitoring.secure_password
--------------------------------------------------
deprecated[The insecure way of storing sensitive data (`url`, `user` and `password`)
in the configuration file or the cluster settings is deprecated]
deprecated[The insecure way of storing sensitive data (`url`, `user` and `password`) in the configuration file or the cluster settings is deprecated]
To avoid credentials that transit in clear text over the network, {watcher} will
reject `url` settings like `http://internal-jira.elastic.co` that are based on

3
docs/en/watcher/actions/pagerduty.asciidoc
View File

@ -153,8 +153,7 @@ must specify an account name and integration key, (see <<secure-settings,secure
bin/elasticsearch-keystore add xpack.notification.pagerduty.account.my_pagerduty_account.secure_service_api_key
--------------------------------------------------
deprecated[Storing the service api key in the YAML file or via cluster
update settings is still supported, but the keystore setting should be used]
deprecated[Storing the service api key in the YAML file or via cluster update settings is still supported, but the keystore setting should be used]
You can also specify defaults for the <<pagerduty-event-trigger-incident-attributes,
PagerDuty event attributes>>:

3
docs/en/watcher/actions/slack.asciidoc
View File

@ -200,8 +200,7 @@ name and webhook URL in the elasticsearch keystore (<<secure-settings,secure set
bin/elasticsearch-keystore add xpack.notification.slack.account.monitoring.secure_url
--------------------------------------------------
deprecated[You can also configure this via settings in the `elasticsearch.yml` file,
using the keystore is the preferred and secure way of doign this]
deprecated[You can also configure this via settings in the `elasticsearch.yml` file, using the keystore is the preferred and secure way of doing this]
You can also specify defaults for the {ref}/notification-settings.html#slack-account-attributes[Slack
notification attributes]: