Conversation
Add IT to validate user creation with just mandatory fields
Turned UsageMetric and UsageMetricTU indices from static index descriptors to template-based descriptors. This change enables index rollover, retention, and lifecycle management for usage metric data, aligning with the approach used for high-volume operational/process data indices.
Introduces `UsageMetricsArchiverJob` to archive `usage-metric` and `usage-metric-tu` documents using the existing batch move (reindex + delete) pattern.
The test fails because it simulates upgrading from the previous platform version (8.8.x), which creates usage-metric indices as concrete indices. The current code expects these to be managed via index templates. This leads to mapping assertion failures. Disabling the test until the template conversion is backported to the previous stable branch and upgrade compatibility is ensured.
## Description Fixes some wrong or flaky tests - fixed wrong order in RdbmsPurger (only worked in second run on empty DB) - fixed flaky BatchOperation test (only worked in second run on empty DB) - added missing RoleMember filters (only worked in second run on empty DB)
## Description On user creation only `username` and `password` should be mandatory. Currently, in the [docs](https://docs.camunda.io/docs/next/apis-tools/orchestration-cluster-api-rest/specifications/create-user/) all fields apart from name are mandatory. On the client side we have validation for all fields on user creation: ``` ArgumentUtil.ensureNotNull("username", request.getUsername()); ArgumentUtil.ensureNotNull("email", request.getEmail()); ArgumentUtil.ensureNotNull("name", request.getName()); ArgumentUtil.ensureNotNull("password", request.getPassword()); ``` We also do not handle null values for `name` and `email` in `UserRecord` I've tested the below scenario (as per ticket test case): Creating a user: <img width="953" height="265" alt="Screenshot 2025-09-18 at 11 25 16" src="https://github.com/user-attachments/assets/85c28c32-a5cf-4c49-af5d-3faa562a3e7f" /> Calling get current user response: <img width="511" height="365" alt="Screenshot 2025-09-18 at 11 26 46" src="https://github.com/user-attachments/assets/86a66cb9-f969-4f99-a4fc-a377ad0bfa9f" /> ## Checklist <!--- Please delete options that are not relevant. Boxes should be checked by reviewer. --> - [x] Enable backports when necessary (fex. [for bug fixes](https://github.com/camunda/camunda/blob/main/CONTRIBUTING.md#backporting-changes) or [for CI changes](https://github.com/camunda/camunda/wiki/CI-&-Automation#when-to-backport-ci-changes)). ## Related issues closes #38324
## Description Adds the missing unassignMappingRuleFromTenant command to the Camunda Java Client that exposes the `DELETE /v2/tenants/:tenantId/mapping-rules/:mappingRuleId` API endpoint. ## Checklist <!--- Please delete options that are not relevant. Boxes should be checked by reviewer. --> - [ ] Enable backports when necessary (fex. [for bug fixes](https://github.com/camunda/camunda/blob/main/CONTRIBUTING.md#backporting-changes) or [for CI changes](https://github.com/camunda/camunda/wiki/CI-&-Automation#when-to-backport-ci-changes)). ## Related issues closes #35771
## Description Fixes context path handling at login and logout. ## Demo Since I am not very familiar with this part, here's a demo how it works. https://github.com/user-attachments/assets/64c53aee-18f1-4d25-8fea-3e15ae6651d5 ## Related issues closes #37616
## Description Fix value type in payload in test
For improved performance.
) ## Description This PR closes the remaining gaps for usage-metrics retention on ES/OS by: - Converting the `usage-metric` and `usage-metric-tu` indices to template descriptors (enables time-based rollover and lifecycle actions). - Adding a `UsageMetricsArchiverJob` that archives documents via our existing reindex + delete batch pattern. ### Why: Previously, a custom ILM policy existed but wasn’t applied anywhere, and the usage-metrics indices did not roll over. As a result, retention (e.g., 730d) couldn’t be enforced, and shards would grow indefinitely. This PR aligns usage-metrics with our batch-operation/process indices approach. ### What was changed: - Converted the `usage-metric` and `usage-metric-tu` indices to template descriptors. - Added new archiver job (`UsageMetricsArchiverJob`) to move aged documents to dated indices and purge source segments, matching our established batch-archive strategy. - Tests verifying archive batch behavior. ### Impact / compatibility: - No schema/API changes. - Existing data remains intact; newly created dated indices will be governed by ILM. ## Checklist <!--- Please delete options that are not relevant. Boxes should be checked by reviewer. --> - [ ] Enable backports when necessary (fex. [for bug fixes](https://github.com/camunda/camunda/blob/main/CONTRIBUTING.md#backporting-changes) or [for CI changes](https://github.com/camunda/camunda/wiki/CI-&-Automation#when-to-backport-ci-changes)). ## Related issues closes #34709
## Description <!-- Describe the goal and purpose of this PR. --> Skip failing tests which are due to bugs and increase timeout for flaky test. Also, increased error handling for easier debugging upon test failure. Successful test run [ here](https://github.com/camunda/camunda/actions/runs/17908078120). ## Checklist <!--- Please delete options that are not relevant. Boxes should be checked by reviewer. --> - [ ] Enable backports when necessary (fex. [for bug fixes](https://github.com/camunda/camunda/blob/main/CONTRIBUTING.md#backporting-changes) or [for CI changes](https://github.com/camunda/camunda/wiki/CI-&-Automation#when-to-backport-ci-changes)). ## Related issues closes #
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )