Task #4926
Story #4082: As a plugin writer I can use plugin_template to bootstrap or update a plugin
switch template entirely to jinja
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Plugin Template
Sprint:
Sprint 54
Quarter:
Description
This task does not affect generate_travis_config.
1. Create a new CLI with 1 command `bootstrap`.
2. Modify all string formatting templates to jinja
The bootstrap command will only need to accept 1 argument "name". Implement this as a positional arg, but it will be replaced in a later story by yaml config.
Associated revisions
History
#1
Updated by amacdona@redhat.com over 2 years ago
- Parent task set to #4082
- Tags Plugin Template added
#2
Updated by dkliban@redhat.com over 2 years ago
- Groomed changed from No to Yes
- Sprint Candidate changed from No to Yes
- Sprint set to Sprint 54
#3
Updated by amacdona@redhat.com over 2 years ago
- Status changed from NEW to POST
- Assignee set to amacdona@redhat.com
#4
Updated by amacdona@redhat.com over 2 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset plugin_template|df12565c13d2f44eaa4a3a3f1bfaff883f968d8e.
#5
Updated by bmbouter about 2 years ago
- Sprint/Milestone set to 3.0.0
#6
Updated by bmbouter about 2 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
.
Use jinja2 to template all files
Primary change: use jinja templates rather than string substitution.
Secondary change: rework the mechanisms of the plugin template to allow templating each of files in the selected section.
https://pulp.plan.io/issues/4926 fixes #4926