When explicitly configured, cloud-init needs to honor the datasource configuration and ignore any secondary datasource validation on the system. The user told us so, so cloud-init should commit to it.
Plans are to 'force' the configuration datasource regardless of cloud-init's detection algorithms if only one datasource is configured.
When explicitly configured, cloud-init needs to honor the datasource configuration and ignore any secondary datasource validation on the system. The user told us so, so cloud-init should commit to it.
Plans are to 'force' the configuration datasource regardless of cloud-init's detection algorithms if only one datasource is configured.