microsoft/HydraLab

Suggest we migrate this to application.yml and make it configurable at the agent level, and the agent admin can specify this themselves.

Open

#247 opened on Feb 1, 2023

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Java (1,027 stars) (104 forks)user submission
help wanted

Description

Suggest we migrate this to application.yml and make it configurable at the agent level, and the agent admin can specify this themselves.

We may do this in another PR.

Originally posted by @hydraxman in https://github.com/microsoft/HydraLab/pull/245#discussion_r1092799321

Contributor guide

Tech stack
java
Domain
backenddevops
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.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
JavaSpring Boot configurationunderstanding of HydraLab architecture
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
First, review the discussion in PR #245 linked in the issue to understand the current implementation and the specific configuration that needs to be migrated. Then, explore the existing application.yml or similar configuration files in the repository to identify where the change should be applied. The goal is to make the configuration agent level, so you'll need to understand the agent's configuration structure. After that, implement the migration, ensuring backward compatibility, and update any tests or documentation accordingly.