As long as this matches the build environment, this does not make a differenece, but let us not depend on this. This will be useful when automatically transforming dnf to rpm pipelines, as the platform_module_id is needed as input to osbuild-composer's dnf-json tool. Performed using this script: ``` cat $1 | jq '(.stages[]? | select(.name == "org.osbuild.dnf") | .options.module_platform_id) |= . + "platform:f30"' | sponge $1 cat $1 | jq '(.build.pipeline.stages[]? | select(.name == "org.osbuild.dnf") | .options.module_platform_id) |= . + "platform:f30"' | sponge $1 ``` Signed-off-by: Tom Gundersen <teg@jklm.no>
20 lines
421 B
JSON
20 lines
421 B
JSON
{
|
|
"stages": [
|
|
{
|
|
"name": "org.osbuild.dnf",
|
|
"options": {
|
|
"releasever": "30",
|
|
"basearch": "x86_64",
|
|
"repos": [
|
|
"sha256:9f596e18f585bee30ac41c11fb11a83ed6b11d5b341c1cb56ca4015d7717cb97"
|
|
],
|
|
"packages": [
|
|
"@Core",
|
|
"selinux-policy-targeted",
|
|
"grub2-pc"
|
|
],
|
|
"module_platform_id": "platform:f30"
|
|
}
|
|
}
|
|
]
|
|
}
|