Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

cloudapi/v2: ensure only one image per a compose in the API spec #1912

Merged
merged 3 commits into from
Oct 13, 2021
Merged

cloudapi/v2: ensure only one image per a compose in the API spec #1912

merged 3 commits into from
Oct 13, 2021

Commits on Oct 13, 2021

  1. cloudapi/v2: move multi-image compose check to the beginning 

    Signed-off-by: Ondřej Budai <ondrej@budai.cz>
    @ondrejbudai
    ondrejbudai committed Oct 13, 2021
    Configuration menu
    Copy the full SHA
    abcc21f View commit details
    Browse the repository at this point in the history

  2. cloudapi/v2: clean up targets 

    tbh, I don't fully understand why we wrote the code in this way.

Not a functional change.

Signed-off-by: Ondřej Budai <ondrej@budai.cz>
    @ondrejbudai
    ondrejbudai committed Oct 13, 2021
    Configuration menu
    Copy the full SHA
    27b4e60 View commit details
    Browse the repository at this point in the history

  3. cloudapi/v2: ensure only one image per a compose in the API spec 

    We've never had the ability to build multiple images per a compose, this
commit thus rips out support for this on the API level:

image_requests is now image_request and it accepts only one ImageRequest
object instead of an array of them.

Signed-off-by: Ondřej Budai <ondrej@budai.cz>
    @ondrejbudai
    ondrejbudai committed Oct 13, 2021
    Configuration menu
    Copy the full SHA
    aa41935 View commit details
    Browse the repository at this point in the history