cloud.cfg mentions the old name:

+# Adapted default config for SUSE CASP systems

Should probably be adjusted in a future submission

And we probably need some way to get around the 'have Choice'

have choice for cloud-init-config = 0.7 needed by cloud-init: cloud-init-config-caasp cloud-init-config-suse

You will get even more "have choice" if the public cloud team submits their configs for the public cloud ... In the end you need a different cloud.cfg file depending on in which cloud or on which product you are using cloud-init.

cloud-init-config-suse is not very usefull, in real world usage, we overwrite that cloud.cfg when creating the image.

Dominique Leuenberger (dimstar) - about 7 years ago

reviewer

so - the question will still be how the OBS prjconf should be setup - does it matter during build which config you get assigned? Or is 'any' really good enough?

---

Dominique Leuenberger (dimstar) - about 7 years ago

reviewer

From the looks, it seems like a

Ignore: cloud-init:cloud-init-config

seems to be the most appropriate: during the build phase it simply does not matter

and in all other cases I'd assume a pattern to take care of the choice

---

Thorsten Kukuk (kukuk) - about 7 years ago

author source maintainer

Correct, either ignore it or default to the config-suse variant by default for building. For the products, product specification or patterns have to take care.

@dimstar_suse, @factory-repo-checker: review reminder