Support adding or removing PPAs to the image

[dilyn-corner]

Check existing issues

• I've verified that this request isn't described by any existing issues.

Request

Describe the feature you'd like to see implemented.

It should be possible to add or remove PPAs and archives in (overlay)/etc/apt/sources.list{,.d}. It would be ideal if I could specify a list of PPAs, some only required for producing the image (e.g. it provides some package only required in an overlay-script but not at runtime), as well as for removing an included PPA (namely, the default one, so that I could provide my own preset mirror).

The problem it solves

Describe the impact your request would have.

I have to add the PPAs I need for an image to the package-repositories list in my imagecraft.yaml and then copy the key and source.list file from the build environment into the rootfs manually.

[lengau]

It sounds like each package repository might be:

• Build environment only
• Final environment only(?)
• Both

I'm not completely certain on the utility of the second bullet point so maybe we don't need that, but we'll need to consider how to do that without duplicating each item.

(NOTE: This is separate from adding private archives)

[syncronize-issues-to-jira]

Thank you for reporting your feedback to us!

The internal ticket has been created: https://warthogs.atlassian.net/browse/IMAGECRAFT-110.

This message was autogenerated

[dilyn-corner]

While the second bullet point could be satisfied by other means (MAAS, cloud-init, a million other ways), I think it would be useful to have it supported here because we'll "already have the image open", might as well slide some extra sauce inside.

[lengau]

@dilyn-corner my main question is whether there's a use case for having it in the final environment when we would specifically want to exclude it from the build environment.

[dilyn-corner]

One use-case would be an archive mirror which is only available at the eventual site the machine is at where the image will be deployed (some sort of air-gap scenario, in a way). Having it available in the build environment would pose issues when e.g. fetching build packages (the apt update would fail, causing a build failure).