Add Disk Queue configuration

[leehinman]

What does this PR do?

In configuration file we will have:

queue:
  disk:
    path:
    max_size:
    segment_size:
    read_ahead:
    write_ahead:
    retry_interval:
    max_retry_interval:
    encryption_password:
    use_compression:

These are the same as beats except for
use_compression, and encryption_password. Which are new to
support encryption & compression.

Why is it important?

Need to be able to configure the disk queue to use it in the shipper.

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.md or CHANGELOG-developer.md.

How to test this PR locally

mage integrationTest

Related issues

• Close add disk queue configuration to shipper configuration #119

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

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @leehinman? 🙏.
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]

💚 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-10-25T15:27:34.226+0000

• Duration: 12 min 45 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

[cmacknz]

Generally looks good, a few questions about tests and how we should get the encryption key.

Please review elastic/elastic-agent#1527 and make sure the configuration there is in sync with this one. Likely this we have another variant of the shared configuration problem between the agent and the shipper, where we have no way to guarantee the two configs stay in sync yet.

[fearful-symmetry]

Might be best to use the "github.com/stretchr/testify/require" library we use everywhere else; will clean up the tests at least.

[leehinman]

reworked with require, also added an environment Fatalf, so when the test fails you see the stdout & stderr so you have some idea what happened.

[fearful-symmetry]

A little worried that the hard-coded ports are going to collide with something, but it looks like the rest of the tests already do that, so unless you're particularly interested in modifying the framework to assign random free ports, that's probably a task for another day.

[leehinman]

yeah it is a risk. Going to wait and see if it is a problem. If it is, my guess is we should move to Docker for starting the Shipper.