Actions
Issue #7933
closedWhen files are moved/removed in the plugin_template, they are not updated in plugins
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Plugin Template
Sprint:
Sprint 87
Quarter:
Description
Steps to reproduce:
mv templates/github/.ci/scripts/release_requirements.txt.j2 templates/github/.ci/assets/
./plugin-template --github pulp_file
pulp_file will end up with a new .ci/assets/release_requirements.txt
file but the old .ci/scripts/release_requirements.txt
remains.
This could lead to lots of outdated and unused files in plugins.
Updated by daviddavis over 2 years ago
This is a bit challenging to solve. A couple options I thought of:
- Keep a list of deprecated files. Whenever a file is moved/removed, we need to add it to this deprecated list. When the plugin_template finds one of these files, it either:
- issues a warning or
- it automatically deletes the file.
- Add a changelog entry whenever we move or remove files.
Updated by daviddavis over 2 years ago
- Subject changed from When files are moved in the plugin_template, they are not moved in plugins to When files are moved/removed in the plugin_template, they are not updated in plugins
Updated by pulpbot over 2 years ago
- Status changed from NEW to POST
Updated by fao89 over 2 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 87
Added by daviddavis over 2 years ago
Updated by daviddavis over 2 years ago
- Status changed from POST to MODIFIED
Applied in changeset plugin_template|00480ae8958b9e72dac5608c96106c4e2a586d43.
Updated by ttereshc about 2 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Added a deprecation check for moved or removed files
fixes #7933