0.47

Minimum required atomic-reactor version

• 1.6.31

Default arrangement version is 6.

API changes

• get_build_request takes an optional arrangement_version argument, and returns a BuildRequestV2 object if arrangement_version is greater than or equal to 6.
• BuildRequestV2 objects ignore most arguments passed in via set_params, as those arguments are retrieved from the REACTOR_CONFIG config map at runtime. the remaining arguments are stored in the USER_PARAMS field of the the build_json['spec']['strategy']['custom_strategy']['env']
• new API call render_plugins_configuration takes the json from USER_PARAMS and returns the json of the atomic-reactor plugins configuration, much like BuildRequest.render() did in previous arrangements
• Backup builder command no longer backs up Build OpenShift objects
• Use ImageStreamImport API for updating tags

Build JSON changes

• ['spec']['strategy']['custom_strategy']['env']['USER_PARAMS'] field added
• ['spec']['strategy']['custom_strategy']['env']['ATOMIC_REACTOR_PLUGINS'] field removed. atomic-reactor generates the plugin configuration from the USER_PARAMS and REACTOR_CONFIG config map at run time.
• most plugin arguments are retrieved at runtime from the REACTOR_CONFIG config map at run time.
• pre_check_and_set_platforms added to orchestrator_inner:6.json as an optional plugin
• check_platforms argument added to pull_base_image
• run check_and_set_rebuild plugin earlier for arrangement 6

Bug Fixes

• The 'architecture' parameter for the orchestrate_build plugin is now set correctly
• ensure_image_stream_tag now retries the operation if a conflict occurs
• usernames shorter than 4 characters are no longer padded to length, since newer Docker versions no longer require that
• BuildRequestV2 sets correct outer template for orchestrator and worker builds
• reactor_config_map and reactor_config_override are ignored for arrangement 5 and lower
• load_exported_image for pulp_push in arrangement 6

Improvements

None