feat: declarative config applied idempotently

Open
  • Is something wrong?
#422 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
typescript
Domain
backend, devops

Research direction

The issue names no files, tests or entry points, so there is no starting code. Before writing anything, ask the maintainers which file format and which entities (clients, roles, providers, policies) the config should cover, and how a plan output should look. Done means a reviewed config file can reproduce a deployment and a dry-run plan is printed before any change is applied.

Written by the indexing model from the issue text.

Description

easy P1 v1.0

Why

Clicking through a console does not scale or review well.

What

  • One file describing system config, clients, roles, providers and policies
  • Applied idempotently at startup or on command, with a plan output first

Done when

A deployment can be reproduced from one reviewed file.

Dominant language
TypeScript
Stars
2
Forks
2
Avg merge
11h 40m
Merged PRs (30d)
104

Getting set up

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 fells-code/seamless-auth-api

All issues in fells-code/seamless-auth-api

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.