nocloud-net doesn't read included network-config file if using seedfrom=URL

This bug was originally filed in Launchpad as [LP: #1809277](https://bugs.launchpad.net/cloud-init/+bug/1809277)

Launchpad details

affected_projects = []

assignee = None

assignee_name = None

date_closed = None

date_created = 2018-12-20T16:11:41.584329+00:00

date_fix_committed = None

date_fix_released = None

id = 1809277

importance = low

is_complete = False

lp_url = https://bugs.launchpad.net/cloud-init/+bug/1809277

milestone = None

owner = raharper

owner_name = Ryan Harper

private = False

status = triaged

submitter = raharper

submitter_name = Ryan Harper

tags = []

duplicates = []

_Launchpad user **Ryan Harper(raharper)** wrote on 2018-12-20T16:11:41.584329+00:00_

Currently nocloud-net does not process network-config file if included in the seed provided via a URL. This is by-design, however, now that several datasources have this model of using an ephemeral DHCP process to fetch user/metadata, which includes network-configuration and then apply that; nocloud-net could transition to this model.

Start by tracing nocloud-net handling of seedfrom=URL and how the included seed contents are processed. Compare the current behavior with the issue’s requested transition to fetching and applying network configuration, then identify suitable regression coverage. Done means an included network-config file is processed when the seed is provided by URL.

Written by the indexing model from the issue text.