Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More details for version constraints in the Puppetfile? #117

Open
fr3nch13 opened this issue Jul 25, 2024 · 0 comments
Open

More details for version constraints in the Puppetfile? #117

fr3nch13 opened this issue Jul 25, 2024 · 0 comments

Comments

@fr3nch13
Copy link

(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

@fr3nch13 fr3nch13 changed the title More details for constraints in the Puppetfile? More details for version constraints in the Puppetfile? Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant