Possibly 'config' modules could specify via some module function that tells cloud-init if that module can be ran without a datasource. Then these modules can be ran even if a datasource is not found or is not fetched correctly. They would of course operate in a limited state (using whatever config that cloud-init can find)
Possibly 'config' modules could specify via some module function that tells cloud-init if that module can be ran without a datasource. Then these modules can be ran even if a datasource is not found or is not fetched correctly. They would of course operate in a limited state (using whatever config that cloud-init can find)