Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Use dynaconf for settings management

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start by mapping the existing configuration management and comparing it with dynaconf's configuration override and persistent user-config capabilities. Check the linked schema type hint dependency before defining the migration scope; done means the application uses dynaconf consistently and the stated configuration goals are supported.

Written by the indexing model from the issue text.

Description

refactor

The configuration management started to grow and its really messy.

Switching to dynaconf should:

  • make it easier to manage config overrides inside the application
  • enable future support for persistent user-config

Also, I wanna leverage Schema type hint support when it gets merged.

Dominant language
HTML
Stars
2
Forks
17
Avg merge
7d 18h
Merged PRs (30d)
3

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 pulp/pulp-docs

All issues in pulp/pulp-docs

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.