Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(vpc-cni): allow logLevel & logFile to be set, or defaulted if not #274

Merged
merged 1 commit into from
Nov 7, 2019

Conversation

metral
Copy link
Contributor

@metral metral commented Nov 6, 2019

Proposed changes

  • fix(vpc-cni): allow logLevel & logFile to be set, or defaulted if not

Removing both settings from the raw YAML manifest, and defaulting its
values to what upstream uses allows for proper configuration
of the settings, rather than trying to retroactively patch the YAML.

Note, the YAML file is intact with upstream with the exception of the changes in this PR. Other than this change, we should not drift from upstream to maintain parity.

Related issues (optional)

Fixes #273

Removing both settings from the raw YAML manifest, and defaulting its
values to what upstream uses allows for proper configuration
of the settings, rather than trying to retroactively patch the YAML.
Copy link
Member

@lukehoban lukehoban left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@metral metral merged commit 783aa75 into master Nov 7, 2019
@pulumi-bot pulumi-bot deleted the metral/fix-vpc-options branch November 7, 2019 03:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cannot change logLevel of aws-k8s-cni
3 participants