Inventory terraform_state - improve backend_config_files option description

[akira6592]

SUMMARY

The backend_config_files option of terraform_state inventory plugin should be specify absolute path.

Due to terraform init command be executed at temporary directory, terraform can not find the backend config file that specified with related path.

In addition to example absolute path /path/to/config1, I explicitly added it to the description.

ISSUE TYPE

• Docs Pull Request

COMPONENT NAME

ADDITIONAL INFORMATION

N/A

[softwarefactory-project-zuul[bot]]

Build succeeded. https://ansible.softwarefactory-project.io/zuul/buildset/1c773dcb34f84d75af133f59c8774a10

:heavy_check_mark: ansible-galaxy-importer SUCCESS in 3m 25s :heavy_check_mark: build-ansible-collection SUCCESS in 8m 22s

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 79.49%. Comparing base (8c52bf2) to head (3490f98). Report is 9 commits behind head on main.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #120 +/- ## ========================================== + Coverage 73.00% 79.49% +6.49% ========================================== Files 16 23 +7 Lines 1015 1434 +419 Branches 182 252 +70 ========================================== + Hits 741 1140 +399 - Misses 243 252 +9 - Partials 31 42 +11 ``` | [Flag](https://app.codecov.io/gh/ansible-collections/cloud.terraform/pull/120/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=ansible-collections) | Coverage Δ | | |---|---|---| | [sanity](https://app.codecov.io/gh/ansible-collections/cloud.terraform/pull/120/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=ansible-collections) | `?` | | | [units](https://app.codecov.io/gh/ansible-collections/cloud.terraform/pull/120/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=ansible-collections) | `79.49% <ø> (+6.88%)` | :arrow_up: | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=ansible-collections#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[akira6592]

Thank you for merging

[patchback[bot]]

Backport to stable-2: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply d9756afa152f2fbf881aab6553191920df27f70d on top of patchback/backports/stable-2/d9756afa152f2fbf881aab6553191920df27f70d/pr-120

Backporting merged PR #120 into main

1. Ensure you have a local repo clone of your fork. Unless you cloned it from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these instructions you'll refer to it by the name upstream. If you don't have it, here's how you can add it:

   $ git remote add upstream https://github.com/ansible-collections/cloud.terraform.git

3. Ensure you have the latest copy of upstream and prepare a branch that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-2/d9756afa152f2fbf881aab6553191920df27f70d/pr-120 upstream/stable-2

4. Now, cherry-pick PR #120 contents into that branch:

   $ git cherry-pick -x d9756afa152f2fbf881aab6553191920df27f70d

   If it'll yell at you with something like fatal: Commit d9756afa152f2fbf881aab6553191920df27f70d is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x d9756afa152f2fbf881aab6553191920df27f70d

5. At this point, you'll probably encounter some merge conflicts. You must resolve them in to preserve the patch from PR #120 as close to the original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-2/d9756afa152f2fbf881aab6553191920df27f70d/pr-120

7. Create a PR, ensure that the CI is green. If it's not — update it so that the tests and any other checks pass. This is it! Now relax and wait for the maintainers to process your pull request when they have some cycles to do reviews. Don't worry — they'll tell you if any improvements are necessary when the time comes!

🤖 @patchback I'm built with octomachinery and my source is open — https://github.com/sanitizers/patchback-github-app.