Andrew Scribner

This is similar to but different from canonical/kubeflow-ci#127: * canonical/bundle-kubeflow#811 (here) proposes we automate the github repository settings * canonical/kubeflow-ci#127 proposes we detect divergence in the *content* of the repo.

In general I think this is a great proposal. This to me has been one of the bigger gaps in Kubeflow ever since the previous attempt was archived. There's details...

@Barteus can you elaborate what you'd like achieved a little more? I could see this going a few different ways. Are any of these what you were thinking? 1. make...

A really easy mistake in a rockcraft.yaml file is to do: ```yaml override-build: command1 command2 ``` when you mean: ```yaml override-build: | command1 command2 ``` Should we warn for this...

Another useful test would be a negative file match, for example to assert `/x/y/z` is NOT in the final rock. This is useful to ensure we do not prime things...

This is similar to #783

One item to note here is that in the past even when we've pinned to a snap channel, we've been burned by broken CI later due to bugs or backwards...

link for the comment above about how we ship different images than we test: https://github.com/canonical/bundle-kubeflow/issues/766

I see istio-pilot listed here, but I don't see the CI that is breaking. Is istio-pilot blocked by this too?

of course it has to be intermittent ... :/