enhancement(deployment): include http provider config in containers

[eldondevat]

Several container deployment platforms (ECS is one example) provide semantics for deploying containers, but lack the configmap semantic used to mount config into containers. This enhancement enables the use of the published containers configured via URL by modifying the container command and providing a location via an environment variable.

Summary

This adds an additional minimal config to the container which uses the http provider and an environment variable to configure vector without modifying the filesystem.

How did you test this PR?

Built a container with this config, and verified that deploying it with a specific env var and command produced the expected configuration. I may need to do some additional testing but am not set up to execute the full vector builds locally, and was hoping for a bit of feedback early.

Change Type

• Bug fix
• New feature
• Non-functional (chore, refactoring, docs)
• Performance

Is this a breaking change?

• Yes
• No

Does this PR include user facing changes?

• Yes. Please add a changelog fragment based on our guidelines.
• No. A maintainer will apply the no-changelog label to this PR.

References

[eldondevat]

@vectordotdev/vector I'd like a maintainer perspective on this if possible. Thanks!