Add sane defaults for database_config_whitelist, add a task to remove non-whitelisted configs #1077
No reviewers
Labels
No labels
approved, awaiting change
broken setup
bug
cannot reproduce
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs change/feedback
needs docs
needs tests
not a bug
not our bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AkkomaGang/akkoma!1077
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "mkljczk/akkoma:akkoma-database-config-whitelist"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I don’t use and aren’t too familiar with db config, so I’ll leave proper review and merge for others.
However I already noticed that one of the whitelisted section simply doesn’t exist, indicating this default cherry-picked from Pleroma might need (possibly more than this one removal) adjustments for Akkoma
@ -569,0 +571,4 @@{:cors_plug},{:ex_aws, :s3},{:mime},{:prometheus, Pleroma.Web.Endpoint.MetricsExporter},this config section does not exist
I recall checking whether this group is present in Akkoma and I thought I removed it before committing…
i do use DB config extensively, and this seems good to me
i'm happy to take this as-is and fix the changelog thingy myself, works on ihba - thanks!
@ -0,0 +1 @@Add reasonable defaults for :database_config_whitelistextremely minor, we use the old changelog format rather than the new changelog.d