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

accesskey should be accessKey #196

Merged
merged 1 commit into from
Sep 17, 2019
Merged

accesskey should be accessKey #196

merged 1 commit into from
Sep 17, 2019

Conversation

strangeminds
Copy link
Contributor

Description

helm upgrade collection sumologic/sumologic -f values.yaml is failing. The helm file setup-job.yaml is looking for accessKey, but the values.yaml is set to accesskey.

Testing performed
  • ci/build.sh
  • Redeploy fluentd and fluentd-events pods
  • Confirm events, logs, and metrics are coming in

helm upgrade collection sumologic/sumologic -f values.yaml is failing.  The file setup-job.yaml is looking for accessKey, but the values.yaml is set to accesskey.
@rvmiller89 rvmiller89 mentioned this pull request Sep 17, 2019
3 tasks
@maimaisie maimaisie merged commit aab5c63 into SumoLogic:master Sep 17, 2019
psaia pushed a commit to psaia/sumologic-kubernetes-collection that referenced this pull request May 25, 2021
* update to test using heredoc for strings to avoid escape issues

* change parsing to only use core fields

* attempt generic extraction rule using existing fields

Co-authored-by: BrianWanner <BrianWanner@users.noreply.github.com>
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.

None yet

2 participants