Skip to content

FIX: write EJECTOR_SCOPE as JSON and defer the 2.5.2 update scripts - #2313

Merged
NeoPlays merged 2 commits into
stereum-dev:mainfrom
NeoPlays:hotfix
Sep 7, 2026
Merged

NeoPlays merged 2 commits into
stereum-dev:mainfrom
NeoPlays:hotfix

Conversation

@NeoPlays

@NeoPlays NeoPlays commented Sep 7, 2026 •

Copy link
Copy Markdown
Member

Summary

EJECTOR_SCOPE was being written to the ValidatorEjector config as a Python dict repr ({'1': [123]}) instead of JSON ({"1":[123]}). The rendered value of the ejector_scope fact was Python-literal-shaped, so older ansible-core versions coerced it into a dict and then serialized the repr into the file.

This PR drops the intermediate fact and builds the JSON inline in the lineinfile value, matching how oracle_allowlist_changes.yaml already handles it. It also defers the 2.5.2 update scripts to a later release.

Changes

  • tasks/2.5.0/ejector_changes.yaml: removed the ejector_scope fact and build the JSON string inline in the lineinfile value. The set_fact now only reads ejector_image_tag, so the task is renamed to "Read current image tag".
  • molecule/250/verify.yml: added two debug dumps of the ValidatorEjector config (raw text and parsed YAML) after the user assertions, so the written line is visible in the test output.

Verification

molecule test -s 250 passes:

  • actions=7 successful=7 failed=0
  • idempotence converge reports changed=0
  • migrated config contains EJECTOR_SCOPE: '{"2":[42]}'

@NeoPlays
NeoPlays merged commit 2023291 into stereum-dev:main Sep 7, 2026
5 checks passed
@NeoPlays
NeoPlays deleted the hotfix branch September 10, 2026 10:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant