0.36
Minimum required atomic-reactor version
1.6.18
API changes
-
new method
create_orchestrator_build
for creating orchestrator build -
added support in config for:
can_orchestrate
(enables using orchestrator)arrangement_version
(default version of inner template to use when creating orchestrator build)
-
CLI: a new
--orchestrator
option forbuild
to create orchestrator build
which requires argument:--platforms
(name of each platform to use)
-
CLI: a new
--worker
option forbuild
to create worker build
which requires arguments:--platform
(platform name to use)--release
(release value to use)
Build JSON changes
-
For orchestrator builds, there are new build json files,
which have same function as the ones already used, only these are specific for
orchestrator or worker builds.-
Based on
prod.json
there areworker.json
andorchestrator.json
. -
Based on
prod_inner.json
there areorchestrator_inner:1.json
andworker_inner:1.json
,
where1
isarrangement_version
from configuration file, to specify default version. -
Based on
prod_customize.json
there areorchestrator_customize.json
andworker_customize.json
.
-
Bug Fixes
- A typo in the spec (#547)
- Retry on conflict updating labels/annotations (#541)
- avoid dependency problems when installing using pip (#537)
- pass git_branch to builds if available (#536)
- token is considered a valid auth method (#533)
Improvements
-
when running orchestrator build, build_image specified in osbs.conf is passed
to the worker build (worker will use same build_image as orchestrator) -
unique_tag_only configuration is now ignored,
specifying "scratch = true" will always only tag built image with unique tag