Skip to content

Conversation

@simu
Copy link
Member

@simu simu commented Nov 10, 2022

We introduce a new parameter version which is used to define default values for parameters channel and alerts. This change is backwards-compatible, as users can still override parameters channel and alerts.

Checklist

  • PR contains a single logical change (to build a better changelog).
  • Update the documentation.
  • Categorize the PR by setting a good title and adding one of the labels:
    bug, enhancement, documentation, change, breaking, dependency
    as they show up in the changelog.

@simu simu force-pushed the fix/set-clusterlogging-collection-type branch from 560f061 to b3524a8 Compare November 10, 2022 14:46
@simu simu force-pushed the feat/param-version branch 4 times, most recently from f4de671 to 7aa32df Compare November 10, 2022 15:01
@simu simu added the enhancement New feature or request label Nov 10, 2022
We introduce a new parameter `version` which is used to define default
values for parameters `channel` and `alerts`. This change is
backwards-compatible, as users can still override parameters `channel`
and `alerts`.

Because this removes the commit ID based setup for fetching the alert
rules YAML, we also remove the renovate regex manager config to
automatically generate PRs for new alert commit IDs.
@simu simu force-pushed the feat/param-version branch from 7aa32df to 834f103 Compare November 10, 2022 15:55
@simu simu changed the base branch from fix/set-clusterlogging-collection-type to master November 10, 2022 15:55
@simu simu force-pushed the feat/param-version branch from 834f103 to 2f8356a Compare November 10, 2022 15:57
@simu simu requested a review from bastjan November 10, 2022 15:59
Copy link
Member

@bastjan bastjan left a comment

Choose a reason for hiding this comment

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

LGTM

Maybe the docs could be clearer if users are expected to override versions and what versions are tested.

@simu
Copy link
Member Author

simu commented Nov 11, 2022

Maybe the docs could be clearer if users are expected to override versions and what versions are tested.

Any specific sections which you think could be clearer? There'll be more details in the documentation in the follow-up PRs which add support for 5.5

@bastjan
Copy link
Member

bastjan commented Nov 11, 2022

The == version section. I know as a user i could change something but i have no idea what i can change and if I even should.

A link to the additional docs would be sufficient.

@simu simu merged commit 702b2ef into master Nov 11, 2022
@simu simu deleted the feat/param-version branch November 11, 2022 08:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants