Catch-up release documentation (#92411)

* Initial commit * Undo custom id docs (done in separate PR) * Update docs, a bit * fix create api doc * Update docs/user/alerting/action-types/email.asciidoc Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com> * Update docs/user/alerting/alerting-getting-started.asciidoc Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com> * Indent warning Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com>
elastic · Feb 23, 2021 · b337d49 · b337d49
1 parent 8be841a
commit b337d49
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 0 deletions.
diff --git a/docs/api/actions-and-connectors/create.asciidoc b/docs/api/actions-and-connectors/create.asciidoc
@@ -27,6 +27,8 @@ Creates an action.
 `secrets`::
   (Required, object) The secrets configuration for the action. Secrets configuration properties vary
   depending on the action type. For information about the secrets configuration properties, refer to <<action-types,Action and connector types>>.
++
+WARNING: Remember these values. You must provide them each time you call the <<actions-and-connectors-api-update, update>> API.
 
 [[actions-and-connectors-api-create-request-codes]]
 ==== Response code

diff --git a/docs/user/alerting/action-types/email.asciidoc b/docs/user/alerting/action-types/email.asciidoc
@@ -4,6 +4,8 @@
 
 The email action type uses the SMTP protocol to send mail message, using an integration of https://nodemailer.com/[Nodemailer]. Email message text is sent as both plain text and html text.
 
+NOTE: For emails to have a footer with a link back to {kib}, set the <<server-publicBaseUrl, `server.publicBaseUrl`>> configuration setting.
+
 [float]
 [[email-connector-configuration]]
 ==== Connector configuration

diff --git a/docs/user/alerting/alerting-getting-started.asciidoc b/docs/user/alerting/alerting-getting-started.asciidoc
@@ -158,6 +158,7 @@ Pre-packaged *alert types* simplify setup, hide the details complex domain-speci
 If you are using an *on-premises* Elastic Stack deployment:
 
 * In the kibana.yml configuration file, add the <<alert-action-settings-kb,`xpack.encryptedSavedObjects.encryptionKey`>> setting.
+* For emails to have a footer with a link back to {kib}, set the <<server-publicBaseUrl, `server.publicBaseUrl`>> configuration setting.
 
 If you are using an *on-premises* Elastic Stack deployment with <<using-kibana-with-security, *security*>>: