Move all configuration into group file

Open
#32 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
devops

Research direction

No files or tests are named. Start by locating the master scaley configuration and group configuration definitions, then trace where each is loaded and consumed. Done means the separate master configuration is no longer needed and every group carries its own Core API token and reporting URL.

Written by the indexing model from the issue text.

Description

Currently, we track both a group configuration as well as a master scaley configuration.

For the sake of simplicity, these should be combined so that basically every group has its own Core API token and reporting URL.

Dominant language
Go
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from engineyard/scaley

All issues in engineyard/scaley

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.