-
Notifications
You must be signed in to change notification settings - Fork 106
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
PDK ignoring config_defaults.yml delete
values
#924
Comments
This issue has been marked stale because it is open with no recent activity. The PDK 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. |
Workaround required based on the current design which looks at files in the templates directory to then process which ones are unmanaged or deleted.
I guess the alternative would be parsing |
This issue has been marked stale because it is open with no recent activity. The PDK 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. |
With the silent drop (without notice in release notes / changelog) of multiple features with puppetlabs/pdk-templates#510 it is more important than ever when maintaining many projects. |
Describe the bug
When using a forked pdk template, if I want to delete an arbitrary file, I should be able to via config_defaults.yml
To Reproduce
Add the following to config_defaults.yml
Expected behavior
When running PDK update on a module using this template, I'd expect any existing Jenkinsfile to be deleted.
Additional context
PDK 1.18.1 on CentOS7 via RPM
This issue is similar to #444
I can workaround the bug, by adding an empty file to moduleroot. IMO. this shouldn't be required.
The text was updated successfully, but these errors were encountered: