Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFC] Deprecate init and write commands on 4.0.0 #1163

Open
rochacbruno opened this issue Jul 12, 2024 Discussed in #1154 · 1 comment
Open

[RFC] Deprecate init and write commands on 4.0.0 #1163

rochacbruno opened this issue Jul 12, 2024 Discussed in #1154 · 1 comment

Comments

@rochacbruno
Copy link
Member

rochacbruno commented Jul 12, 2024

Discussed in #1154

Originally posted by rochacbruno July 8, 2024
I suggest that on 4.0.0 we remove the following CLI commands

  • init
    • Users will need to write their schema manually so this command will not be very helpful
  • write
    • USers will need to use each source client to write, dynaconf will only read data from sources.

Changes to commands:

  • list
    • cleanup the tabular formatting, remove all coloring

Any comments? is there someone using those commands?

closes #908 #936

@rochacbruno rochacbruno changed the title RFC Changes to the CLI on 4.0.0 [RFC] Deprecate init and write commands on 4.0.0 Jul 12, 2024
@pedro-psb
Copy link
Member

About the init, I think it would be convenient to have an init for boostrapping framework integrations.

For example, have dynaconf init django convert the core settings into pre-populated schema classes, possibly populated with sane default validators and django's own default values.

This is a good candidate for being a dynaconf plugin/extension, as there might be several 3rth party integrations (or plugins of these frameworks) that can potentially want to implement such integration facilities.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants