Skip to content

Conversation

@robin-checkmk
Copy link
Member

Pull request type

Try to limit your pull request to one type, submit multiple pull requests if needed.

Check the type of change your PR introduces:

  • Bugfix
  • Feature
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no API changes)
  • Build related changes
  • Documentation content changes
  • Other (describe what kind of change you performed):

What is the current behavior?

Describe the current behavior that you are modifying, or link to a relevant issue.

There are no lookup plugins for activations.

What is the new behavior?

Describe the behavior or changes that are being added by this PR.

There are lookup plugins for activations. One to list all running activations and one to look up a specific activation.

Other information

Any other information that is important to this PR, e.g screenshots of how the component looks before and after the change.

@robin-checkmk robin-checkmk self-assigned this Dec 31, 2025
@robin-checkmk robin-checkmk changed the title Add lookup modules for activations. Add lookup modules for activations Dec 31, 2025
@robin-checkmk robin-checkmk force-pushed the feature/activation-lookups-and-improvements branch from 06b8730 to 0cb85bf Compare December 31, 2025 16:10
@robin-checkmk robin-checkmk marked this pull request as ready for review December 31, 2025 16:34
@robin-checkmk
Copy link
Member Author

While this is generally ready for review, the code needs a thorough going through and the integration tests are rather limited and might need an additional angle. Please review diligently.

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.

2 participants