kenya-jug/regression

Support Editing and Deleting Registered Data Sources

Open

#50 opened on May 20, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Java (12 forks)auto 404
UIgood first issue

Repository metrics

Stars
 (7 stars)
PR merge metrics
 (PR metrics pending)

Description

Implement functionality to allow users to edit and delete registered data sources, improving management and cleanup of data source configurations.

Current Behavior:

  • Once a data source is registered, it cannot be modified or removed through the UI or API.

Expected Features:

  1. Edit Data Source:

    • Update properties such as name, connection details, or credentials.
    • Validate inputs to prevent misconfiguration.

  2. Delete Data Source:

    • Remove unused or obsolete data sources.
    • Provide confirmation prompts to avoid accidental deletion.
    • Consider handling or warning about dependent applications or data.

Tasks:

  • Add UI controls for editing and deleting data sources.
  • Create corresponding backend API endpoints (PUT /data-sources/{id}, DELETE /data-sources/{id}).
  • Implement validation and permission checks.
  • Handle potential cascading impacts or restrict deletion if dependencies exist.

Benefits:

  • Enhances flexibility in managing data sources.
  • Keeps configuration clean and up-to-date.
  • Supports better system hygiene and administration.

Contributor guide

Research direction
Examine the existing data source registration endpoint and UI component. Follow the same patterns to add PUT and DELETE endpoints with validation and confirmation dialogs. Check for dependency handling before deletion.
Tech stack
javaspringrest api
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaSpring Boot
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70