You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this moment the Collection is able to create an OSTree repository that is "published" using an HTTP server. When you create a new image that then substitutes the previous one (be aware of this [1] issue)... but there is more functionality around OSTree repo management that could be useful.
For example, as OSTree image admin I would like to:
Rollback to a previous OSTree commit (image)
Manage OSTree repo branches, promoting, etc [2] (for development, testing, different major versions, etc)
Create an OSTree repo from TAR files (separately from creating images)
Use external (to the image builder) hosting for the OSTree repo (ie. Ansible Automation Hub)
At this moment the Collection is able to create an OSTree repository that is "published" using an HTTP server. When you create a new image that then substitutes the previous one (be aware of this [1] issue)... but there is more functionality around OSTree repo management that could be useful.
For example, as OSTree image admin I would like to:
[1] #94
[2] https://ostree.readthedocs.io/en/stable/manual/repository-management/
The text was updated successfully, but these errors were encountered: