Skip to content

Don't require package names in pillar data #190

@noelmcloughlin

Description

@noelmcloughlin

The pillar.example illustrates a design problem where, in some scenarios, package names must be defined as pillars. This requirement should be removed or replaced by abstract flags-

  • require_contrib_package = True
  • require_python_package = True

Furthermore, in my opinion, if pillar data includes postgres.extension list then contrib package should be auto-installed. Formula user should not need to know packaging implementation, only how to model their requirements as pillars.

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