api/types/checkpoint: move checkpoint options to client by thaJeztah · Pull Request #50905 · moby/moby (original) (raw)

@thaJeztah

Move the option-types to the client and in some cases create a copy for the backend. These types are used to construct query- args, and not marshaled to JSON, and can be replaced with functional options in the client.

The CreateOptions type was used both as options-struct for the client, and as struct to marshal/unmarshal the request. For this type, a copy is created in the Client and a new checkpoint.CreateRequest is added in the API.

Signed-off-by: Sebastiaan van Stijn github@gone.nl

This was referenced

Sep 5, 2025

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters

[ Show hidden characters]({{ revealButtonHref }})