anchor.diff:  In earlier versions, you could pass both `settings` and `index_settings` in the
   body of a restore snapshot request, but the `settings` value was ignored. The
   restore snapshot API now rejects requests that include a `settings` value.
  +
  +*Impact* +
  +Discontinue use of the `settings` parameter in restore
  +snapshot request. Requests that include these parameters will return an error.
   ====
  
positive.code: now-deprecated path-style access pattern by default. In versions 7.0, 7.1, 7.2
  and 7.3 the `repository-s3` plugin always used the path-style access pattern.
  This is a breaking change for deployments that only support path-style access
  but which are recognized as supporting DNS-style access by the AWS SDK. If your
  deployment only supports path-style access and is affected by this change then
  you must configure the S3 client setting `path_style_access` to `true`. This
  breaking change was made necessary by
  https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-plan-the-rest-of-the-story/[AWS's
  announcement] that the path-style access pattern is deprecated and will be
  unsupported on buckets created after September 30th 2020.
  ====
  
  .Restore requests no longer accept settings.
  
negative.code: previously be used to enable compression for all shared file system repositories where `compress` was not specified.
  The `repositories.fs.compress` setting has been removed.
  
  *Impact* +
  Use the repository specific `compress` setting to enable compression. See
  <<modules-snapshots>> for information on the `compress` setting.
  
  Discontinue use of the `repositories.fs.compress` node-level setting.
  ====
  
  .Metadata files are now compressed by default.
  