-
Notifications
You must be signed in to change notification settings - Fork 17
Fix/113 #117
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
Fix/113 #117
Conversation
7fe2968
to
5077ad2
Compare
@aidaph I have created in this branch some tests for the Cloud and IP records, we should implement them also for the accelerators and the storage records... |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #117 +/- ##
=========================================
Coverage ? 51.29%
=========================================
Files ? 23
Lines ? 1084
Branches ? 117
=========================================
Hits ? 556
Misses ? 520
Partials ? 8 ☔ View full report in Codecov by Sentry. |
80e054c
to
dd230f5
Compare
Fixes: #113 SemVer: bugfix
The `dict` method of the records are, by design, meant to just conver the record to a dictionary, without converting data types. If we want to serialize the records correcty, as we are doing when generating the SSM records, we need to rely on serialization. See [1] for more context. [1]: pydantic/pydantic#5155 (comment) Fixes: #113 SemVer: bugfix
Include missing fields in CloudRecord when being rendered (i.e. remove the `exlude_unset` argument when exporting, and remove versions from rendering. Fixes: #118 SemVer: bufgix
Instead of rendering the individual records in the SSM messenger, the records classes must now implement a `ssm_message` method that provides an export of the mode, with correct serialized values for each field, that the SSM messenger will append to a SSM message.
Fix serialization of fields, using correct method (i.e. JSON serialization always).