Indenting correction for module configuration example

[robin13]

What does this PR do?

Fix YAML indenting for module configuration example

Why is it important?

The example given was invalid

Checklist

- [ ] My code follows the style guidelines of this project
- [ ] I have commented my code, particularly in hard-to-understand areas

• I have made corresponding changes to the documentation
  - [ ] I have made corresponding change to the default configuration files
  - [ ] I have added tests that prove my fix is effective or that my feature works
  - [ ] I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2021-08-23T13:15:09.229+0000

• Duration: 26 min 47 sec

• Commit: 88883d4

Trends 🧪

❕ Flaky test report

No test was executed to be analysed.

[elasticmachine]

Pinging @elastic/integrations (Team:Integrations)

[narph]

hi @robin13 , nice catch , we first update https://github.com/elastic/beats/blob/master/x-pack/filebeat/module/azure/_meta/docs.asciidoc then run mage update which will regenerate the azure.asciidoc file. Mind going on the same route? This is why the build is failing as well.

[robin13]

Hi @narph I don't have the whole build environment for beats set up, and it's a bit daunting for me to do this just for a typo fix...
I have corrected the changes to the correct file now, so perhaps you could do the mage update? :)

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b indenting-correction upstream/indenting-correction
git merge upstream/master
git push upstream indenting-correction

[narph]

LGTM