feat: add container env prefix COM_ALIYUN_META_ENVS_ as custom metas. #275
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As the PR title said, this PR is going to add a handler for container envs which has prefix with
COM_ALIYUN_META_ENVS_, those envs will be processed, and the name which trimmed the prefix would be the actual env name from docker container spec, and the value will be log-pilotcontainerfield name.Since these envs are defined as container metas, I set the magic prefix name to
COM_ALIYUN_META_ENVS_, it fixed #274 .Thanks.