Skip to content

More details for version constraints in the Puppetfile? #117

@fr3nch13

Description

@fr3nch13

(adding here for the future googler)
It doesn't mention in the documentation at either allowed or not.
For the Puppetfile in control-repos, can you define version constraints other than the exact version number?

Like, instead of

mod 'puppetlabs-reboot', '2.0.0'

Can we do something like these?

mod 'puppetlabs-reboot', '~2.0'
mod 'puppetlabs-reboot', '>=2.0.0 <3'
mod 'puppetlabs-reboot', '2.*'

Similar to how Composer describes it at: https://getcomposer.org/doc/articles/versions.md

Can the documentation be updated to be more clear if version ranges are allowed or not? Here at step 2: https://www.puppet.com/docs/puppet/7/puppetfile_usage.html#declare_puppet_forge_modules_in_the_puppetfile

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