get you only snapshot name:
[0] => /1.0/instances/c1/snapshots/k1?project=101
[1] => /1.0/instances/c1/snapshots/k2?project=101
[2] => /1.0/instances/c1/snapshots/A-0?project=101
Along useful information such as [name][expires_at] [created_at] [stateful] [size], it spits for each snapshot the whole story of its attached instance [config][expanded_config][expanded_devices] which leads to a very large output, in case you had some daily plans and lots of snapshots.
Those instance related information are just showing the actual status of container and not related to snapshot.
Once you apply the snapshot to parent container, the config remains anyways the same.
If you create a new instance from it, the config will be either the one you define by profile or otherwise or it should use the config of the parent of snapshot.
BTW, [last_used_at] never changes, what sort of information it supposed to show?
Snapshots include instance config/devices/profiles, so it’s perfectly normal to have them show you that information, it is not duplicated from the parent instance.
When you restore a snapshot, it’s not just the filesystem being reverted but the config too.
Appreciate your feedback.
I have experienced otherwise.
Config is the actual instance config mirrored on snapshot.
So, snapshot seems merely just revert the storage back and no more.
I have container c1 profile x.
Fetch snapshots info, in all i get profile x specific config, 2xcpu, 2G Ram, 1GB storahe etc.
I change the container profile to y.
All previously taken snapshots showing mow the config y.
Use an old snapshot, it exactly creates or reverts back by utilizing newly applied profile.
So, snapshot is headless and don’t need to mimic the config story.