Actions
Task #4928
closed
Implement template `update`
Status:
CLOSED - COMPLETE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Plugin Template
Sprint:
Quarter:
Description
1. determine a list of "managed files" from the yaml config. Managed files should have a comment stating that plugin writers should not manually edit these files.
2. implement `update`, which clobbers all managed files
3. add a yaml field "skip_update_files" which allows the plugin author to skip managed files, if they must edit them.
4. implement --file-path option, which clobbers any file, managed or not. This can be used to create new bootstrap files that have been added since the plugin creation, or replacing files that have changed dramatically.
Related issues
Added by dkliban@redhat.com over 5 years ago
Updated by dkliban@redhat.com over 5 years ago
- Related to Story #4082: As a plugin writer I can use plugin_template to bootstrap or update a plugin added
Updated by dkliban@redhat.com about 4 years ago
- Status changed from NEW to CLOSED - COMPLETE
Actions
.
Problem: can't use a config file when updating plugin
Solution: add ability to use config file
re: #4928 https://pulp.plan.io/issues/4928