odcs

#84 Split /odcs/1/composes/ into two separate endpoints for creating a new compose and renewing a compose
Closed Opened by cqi.

Closed
Reopen Issue

Currently we mix creating new compose and renewing a compose into one endpoint /odcs/1/composes/, all code are put into one big method. This works but could be more clear by separating into two individual endpoints, one endpoint for one operation.

POST to /odcs/1/composes/ could be still for creating a new compose.

POST to /odcs/1/composes/<int:id>/renew/ could be for renewing a compose.

:+1:

Alternatively, you could PATCH to /odcs/1/composes/<int:id> to renew the existing resource.

Either way works for me.

Metadata Update from @cqi:
- Issue assigned to cqi

PR: https://pagure.io/odcs/pull-request/123

Metadata Update from @jkaluza:
- Issue status updated to: Closed (was: Open)

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/pungi/odcs/issues/84

Please continue any further discussion there.
Metadata
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.