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

chore!: remove replacing values in configuration marked by 'replace' suffix #2615

Merged
merged 1 commit into from
Nov 23, 2022

Conversation

kasia-kujawa
Copy link
Contributor

@kasia-kujawa kasia-kujawa commented Nov 18, 2022

chore: remove replacing values in configuration marked by 'replace' suffix
make values in configuration for otelcol dependended on otelcol parameters in values.yaml

removes "otelcol.k8s.cluster.name" which was added in #1721 and it is no longer in use

this pull request reverts changes introduced in #1721

related to #1729

Generated templates have been compared using output of helm template . -f values.yaml -f values_custom.yaml where
values_custom.yaml had following form:

sumologic:
  ## Sumo access ID
  accessId: "dummy"

  ## Sumo access key
  accessKey: "dummy"

  ### Traces configuration
  ## Set the enabled flag to true to enable traces ingestion.
  traces:
    enabled: true

related change in update-collection-v3: SumoLogic/sumologic-kubernetes-tools#382

@github-actions github-actions bot added the documentation documentation label Nov 18, 2022
@kasia-kujawa kasia-kujawa added this to the v3.0 milestone Nov 18, 2022
@kasia-kujawa kasia-kujawa self-assigned this Nov 18, 2022
@kasia-kujawa kasia-kujawa marked this pull request as ready for review November 18, 2022 10:22
@kasia-kujawa kasia-kujawa requested a review from a team as a code owner November 18, 2022 10:22
@kasia-kujawa kasia-kujawa force-pushed the kk-revert-1721 branch 4 times, most recently from d5d1a27 to f37b99a Compare November 18, 2022 12:23
Copy link
Contributor

@sumo-drosiek sumo-drosiek left a comment

Choose a reason for hiding this comment

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

Great. Not sure if we need a migration for that change.

@kasia-kujawa
Copy link
Contributor Author

kasia-kujawa commented Nov 21, 2022

Great. Not sure if we need a migration for that change.

I need to add at least information to migration doc that the mechanism with replacing some configuration values with 'replace' suffix was removed.

related change in update-collection-v3: SumoLogic/sumologic-kubernetes-tools#382

kasia-kujawa added a commit to SumoLogic/sumologic-kubernetes-tools that referenced this pull request Nov 22, 2022
kasia-kujawa added a commit to SumoLogic/sumologic-kubernetes-tools that referenced this pull request Nov 22, 2022
@kasia-kujawa kasia-kujawa changed the title chore: remove replacing values in configuration marked by 'replace' suffix chore!: remove replacing values in configuration marked by 'replace' suffix Nov 22, 2022
@kasia-kujawa kasia-kujawa force-pushed the kk-revert-1721 branch 3 times, most recently from 98dee38 to f9daff2 Compare November 23, 2022 13:28
kasia-kujawa added a commit to SumoLogic/sumologic-kubernetes-tools that referenced this pull request Nov 23, 2022
…suffix

make values in configuration for otelcol dependended on otelcol parameters in values.yaml

removes "otelcol.k8s.cluster.name"  which was added in #1721 and it is no longer in use

this pull request reverts changes introduced in #1721

related to #1729
Copy link
Contributor

@sumo-drosiek sumo-drosiek left a comment

Choose a reason for hiding this comment

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

🎉

@kasia-kujawa kasia-kujawa merged commit 7b80b8a into main Nov 23, 2022
@kasia-kujawa kasia-kujawa deleted the kk-revert-1721 branch November 23, 2022 14:32
kasia-kujawa added a commit to SumoLogic/sumologic-kubernetes-tools that referenced this pull request Nov 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants