Remove ambiguity on Dockerfile CMD.

[mighty1231]

What does this PR do?

Beat binaries have two options, -e and --environment have different use.

This MR reveals new Dockerfile, use of --environment instead -environment, and some change on document.

Why is it important?

Use of -environment increases ambiguity, since beats have -e options, which sends logs for stderr.

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.

Additional Checklist

• Checked any environment flag usage in entire repository with single minus character

Related issues

• Relates [Elastic Agent] Fix RPM and DEB packaging for Elastic Agent #19959
  • Other PR, that changes -environment to --environment

[cla-checker-service]

💚 CLA has been signed

[elasticmachine]

❕ Build Aborted

The PR is not allowed to run in the CI yet

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-05-03T15:47:46.023+0000

• Duration: 5 min 45 sec

Steps errors

Expand to view the steps failures

Error signal

• Took 0 min 0 sec . View more details here
• Description: githubApiCall: The REST API call https://api.github.com/orgs/elastic/members/mighty1231 return the message : java.lang.Exception: httpRequest: Failure connecting to the service https://api.github.com/orgs/elastic/members/mighty1231 : httpRequest: Failure connecting to the service https://api.github.com/orgs/elastic/members/mighty1231 : Code: 404Error: {"message":"User does not exist or is not a member of the organization","documentation_url":"https://docs.github.com/rest/reference/orgs#check-organization-membership-for-a-user"}

🤖 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!)

[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: 2022-06-28T13:15:52.811+0000

• Duration: 130 min 55 sec

Test stats 🧪

Test	Results
Failed	0
Passed	22404
Skipped	1937
Total	24341

💚 Flaky test report

Tests succeeded.

🤖 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]

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 flag_environment upstream/flag_environment
git merge upstream/main
git push upstream flag_environment

[belimawr]

Thanks for the PR @mighty1231! I added only a small comment.

[belimawr]

/test

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[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 flag_environment upstream/flag_environment
git merge upstream/main
git push upstream flag_environment

[belimawr]

this E2E tests seem to be stuck :/

[belimawr]

/test

[belimawr]

@mergify help

[mergify]

Sorry but I didn't understand the command. Please consult the commands documentation 📚.

[belimawr]

I think those E2E tests are not in this branch yet, I'll ask mergify to rebase this PR onto main.

[belimawr]

@Mergifyio rebase

[mergify]

rebase

✅ Branch has been successfully rebased

[belimawr]

/test

[belimawr]

/test

[belimawr]

/test

[belimawr]

@Mergifyio rebase

[mergify]

rebase

✅ Branch has been successfully rebased

[rdner]

/test

[belimawr]

@Mergifyio rebase

[mergify]

rebase

✅ Branch has been successfully rebased

[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 flag_environment upstream/flag_environment
git merge upstream/main
git push upstream flag_environment

[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 flag_environment upstream/flag_environment
git merge upstream/main
git push upstream flag_environment

[mergify]

help

❌ Sorry but I didn't understand the command. Please consult the commands documentation 📚.

[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 flag_environment upstream/flag_environment
git merge upstream/main
git push upstream flag_environment

[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 flag_environment upstream/flag_environment
git merge upstream/main
git push upstream flag_environment

[cmacknz]

Closing. Re-open when ready for re-review.