-
Notifications
You must be signed in to change notification settings - Fork 352
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
Implement an allow list for deployments #1387
Comments
This issue has been marked stale because it has had no activity for 60 days. The Puppet Team is actively prioritizing existing bugs and new features, if this issue is still important to you please comment and we will add this to our backlog to complete. Otherwise, it will be closed in 7 days. |
Yes this is still important |
This issue has been marked stale because it has had no activity for 60 days. The Puppet Team is actively prioritizing existing bugs and new features, if this issue is still important to you please comment and we will add this to our backlog to complete. Otherwise, it will be closed in 7 days. |
"actively" |
This issue has been marked stale because it has had no activity for 60 days. The Puppet Team is actively prioritizing existing bugs and new features, if this issue is still important to you please comment and we will add this to our backlog to complete. Otherwise, it will be closed in 7 days. |
So where on the prio list is it? |
support ticket #01247437 |
Use Case
We already have an option to exclude spec files. But still a lot of useless files can be deployed. With puppetlabs/puppet-specifications#157 we now have a list of allowed files in a module release. r10k needs an option to exclude everything else.
Describe the Solution You Would Like
Implement puppetlabs/puppet-specifications#157
Describe Alternatives You've Considered
Additional Context
The text was updated successfully, but these errors were encountered: