Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Make {tenant_id}-system-user creation idempotent

Description

Based on we have to adjust system-user creation while _tenant API is called.
This is not a module system user. The current system user is created during _tenant, and the user Is used by the mod-scheduler to run jobs.

Scope:

  1. Ensure that user creation is an idempotent operation. If the system user already exists, skip the creation steps and continue the module installation without interruption.

  2. Add tests if needed.

Environment

None

Potential Workaround

None

Checklist

hide

Activity

Show:

Craig McNally January 3, 2025 at 10:30 PM

After discussing with the devs, I’m closing this as won’t do. The idempotency of user creation is already in place. The issue was related to the data on the environment.

Won't Do

Details

Assignee

Reporter

Labels

Priority

Development Team

Eureka

Release

Ramsons (R2 2024) Bug Fix

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created December 2, 2024 at 1:19 PM
Updated January 28, 2025 at 1:52 PM
Resolved January 3, 2025 at 10:29 PM
TestRail: Cases
TestRail: Runs