Skip to content

Move HTTP security to GUCs instead of Cargo features. #374

Description

Currently, the HTTP security level is controlled by three cargo features (

pg_durable/Cargo.toml

Lines 18 to 20 in 69eefdc

http-allow-all = []
http-allow-azure-domains = []
http-allow-test-domains = ["http-allow-azure-domains"]
), which must be enabled or disabled at the time when the extension is built. Ideally, this would be done via one or more Postmaster GUCs (probably SUPERUSER_ONLY), so that it can be changed more flexibly.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions