OSTree Plugin Roadmap » History » Sprint/Milestone 2
jortel@redhat.com, 02/13/2018 10:23 PM
1 | 1 | jortel@redhat.com | # OSTree Plugin Roadmap |
---|---|---|---|
2 | |||
3 | ## Terms |
||
4 | |||
5 | 2 | jortel@redhat.com | **Ref** - A named commit. Think of it as a branch: |
6 | 1 | jortel@redhat.com | |
7 | - Branch path (name). |
||
8 | - Commit ID |
||
9 | - Commit Metadata |
||
10 | 2 | jortel@redhat.com | |
11 | **Commit Metadata** - A set of key/value pairs. |
||
12 | 1 | jortel@redhat.com | |
13 | ## Use Cases |
||
14 | |||
15 | As a user, I want to CRUD an ostree importer. |
||
16 | Additional importer attributes: |
||
17 | |||
18 | - (optional) list of *branches* to pull. The default is (None) to pull all branches. |
||
19 | - (optional) tree traversal *depth*. The default is 0 (shallow). A value of -1 indicates unlimited depth. |
||
20 | - (optional) GPG keys used to validate commits. |
||
21 | |||
22 | As a user, I want to CRUD an ostree publisher. |
||
23 | Additional publisher attributes: |
||
24 | |||
25 | - (optional) tree traversal publishing *depth*. The default is 0 (shallow). A value of -1 indicates unlimited depth. |
||
26 | |||
27 | As a user, I want to synchronize with a remote repository as defined by the feed URL. |
||
28 | Additional options: |
||
29 | |||
30 | - The *repair* option causes the local backing (ostree) repository to be rebuilt. This is needed to deal with corrupted local (ostree) repositories. |
||
31 | - The feed URL can be file://, http:// or https:// |
||
32 | |||
33 | As a user, I want each content (unit) to be a *Ref*. |
||
34 | |||
35 | As a user, I want to list all available *Refs* in the remote repository (by repository). This should be refresh on each sync. |
||
36 | |||
37 | As a user, I want to publish a repository version. |