Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[#7470] Add rake task to convert legacy YAML #7471

Merged
merged 5 commits into from
Dec 19, 2022
Merged

Conversation

gbp
Copy link
Member

@gbp gbp commented Dec 15, 2022

Relevant issue(s)

Fixes #7470

What does this do?

Add rake task to convert legacy YAML

Why was this needed?

In WDTK we have YAML stored which was generate by the old Syck library
which can't be parsed by the newer Psych library.

This rake task fixes the YAML so it can be parsed.

@garethrees garethrees mentioned this pull request Dec 15, 2022
6 tasks
* Always use block code for commands to be run
* Mark commands as required/optional
* Specify version when required commands need to run by
Better represent the order the commands should be run with required
actions before optional ones.
In WDTK we have YAML stored which was generate by the old `Syck` library
which can't be parsed by the newer `Psych` library.

This rake task fixes the YAML so it can be parsed.
In WDTK we have old application objects stored in YAML these can't
always be decoded by Rails. Instead we reload the objects from the
database.

This rake task fixes the YAML so it can be parsed.
Copy link
Member Author

@gbp gbp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have run a variation of these tasks in the Rails production console to ensure the remaining events can now be migrated. With exception on 4 records which hit #7478

@gbp gbp merged commit 679c134 into develop Dec 19, 2022
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.

Migration to JSONB params failing
1 participant