Skip to content

nginx::resource::upstream with no members can only be called once #897

@ikryten

Description

@ikryten

We define upstreams with no members because we use a custom in-house module to resolve the destination. This use to work fine with an older version of the module. But the latest version assumes that if nginx::resource::upstream has no members defined then you want to collect them. That's all well and good but the collection logic is flawed, the collection is done through a class (class { '::nginx::resource::upstream::collect': ) and classes can only be called once. This effectively means you can only have one upstream defined that uses 'collected' members. This should be addressed. It should be a defined type or just done directly in nginx::resource::upstream.

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