ci: run AWS with the terraform config files

[v1v]

What does this PR do?

Unstash the terraform within the node context

Why is it important?

The existing implementation runs all the steps but unfortunately it runs the deleteDir after terraform --apply

Test

hence the cloud specific testing is now using the terraform folder: https://beats-ci.elastic.co/job/Beats/job/beats/job/PR-32774/2/execution/node/2622/log/

[mergify[bot]]

This pull request does not have a backport label. If this is a bug or security fix, could you label this PR @v1v? 🙏. For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[elasticmachine]

:broken_heart: Build Failed

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: 2022-08-23T16:53:24.602+0000

• Duration: 14 min 3 sec

Steps errors

Expand to view the steps failures

Installing github.com/magefile/mage@latest

• Took 0 min 0 sec . View more details here
• Description: go install github.com/magefile/mage@latest

Installing github.com/magefile/mage@latest

• Took 0 min 0 sec . View more details here
• Description: go install github.com/magefile/mage@latest

Installing github.com/magefile/mage@latest

• Took 0 min 0 sec . View more details here
• Description: go install github.com/magefile/mage@latest

:grey_exclamation: Flaky test report

No test was executed to be analysed.

:robot: GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[mergify[bot]]

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 test/aws-specific upstream/test/aws-specific
git merge upstream/main
git push upstream test/aws-specific

[mergify[bot]]

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 test/aws-specific upstream/test/aws-specific
git merge upstream/main
git push upstream test/aws-specific

[mergify[bot]]

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 test/aws-specific upstream/test/aws-specific
git merge upstream/main
git push upstream test/aws-specific

[v1v]

Jenkins sunset and migration to buildkite to happen in the near future, so I'll close this now