NEWS: clarify the osbuild-composer-cloud entry
We expect to merge this into the main osbuild-composer package in the future and change the port it is exposed on, so for now communicate that this is not stable API. Signed-off-by: Tom Gundersen <teg@jklm.no>
This commit is contained in:
parent
782895e4be
commit
eb01680c2e
1 changed files with 5 additions and 4 deletions
9
NEWS.md
9
NEWS.md
|
|
@ -2,10 +2,11 @@
|
|||
|
||||
## CHANGES WITH 21:
|
||||
|
||||
* Composer API is now available in the TODO subpackage. It's meant to be
|
||||
a simple API that allows users build an image and push it to a cloud
|
||||
provider. It doesn't support advanced features like storing blueprints
|
||||
as Weldr API does.
|
||||
* Composer API is now available as a tech preview in the
|
||||
osbuild-composer-cloud subpackage. It's meant to be a simple API that
|
||||
allows users build an image and push it to a cloud provider. It doesn't
|
||||
support advanced features like storing blueprints as Weldr API does. This
|
||||
is not stable API, and is subject to incompatible change.
|
||||
|
||||
* Koji API is now available in the -koji subpackage. It can be used
|
||||
to perform an image build and push the result directly to a Koji
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue