Open cjdcordeiro opened 3 months ago
I agree in the general sense but not with the example: the name, platforms and base are how we keep track of the instances (so we wouldn't know what to clean without them):
❯ lxc --project=rockcraft list
+---------------------------------------------------------------+---------+------+------+-----------+-----------+
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
+---------------------------------------------------------------+---------+------+------+-----------+-----------+
| base-instance-rockcraft-buildd-base-v7-c-a38d05774a6de0cf6ab1 | STOPPED | | | CONTAINER | 0 |
+---------------------------------------------------------------+---------+------+------+-----------+-----------+
| rockcraft-hello-on-amd64-for-amd64-16398450 | STOPPED | | | CONTAINER | 0 |
+---------------------------------------------------------------+---------+------+------+-----------+-----------+
| rockcraft-redis-on-amd64-for-amd64-16519802 | STOPPED | | | CONTAINER | 0 |
+---------------------------------------------------------------+---------+------+------+-----------+-----------+
True, good point. I choose the wrong attribute to remove :laughing: (updating the description)
Bug Description
Some commands, like clean, should not need such a strict schema validation, if all they gonna do is “clean”. IoW, if I want to
clean
my project, the YAML shouldn't have an impact on the operation.To Reproduce
Write a bogus rockcraft.yaml and run
rockcraft clean
.Environment
Any
rockcraft.yaml
Relevant log output