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

Update to zgw-consumers 0.32.0 #4057

Closed
4 tasks done
sergei-maertens opened this issue Mar 25, 2024 · 0 comments · Fixed by #4059
Closed
4 tasks done

Update to zgw-consumers 0.32.0 #4057

sergei-maertens opened this issue Mar 25, 2024 · 0 comments · Fixed by #4059

Comments

@sergei-maertens
Copy link
Member

sergei-maertens commented Mar 25, 2024

  • Update to 0.32.0
  • Remove gemma-zds-client from dependencies
  • Add datamigration to copy global zaaktype default to form-level configuration (similar to objects API config)
  • Remove ListZaaktypenMixin from config field
@sergei-maertens sergei-maertens added this to the Release 2.7.0 milestone Mar 25, 2024
@sergei-maertens sergei-maertens self-assigned this Mar 25, 2024
sergei-maertens added a commit that referenced this issue Mar 25, 2024
Configuration of the fields (defaults) from zgw api group needs to be
stored on the registration backend options so that it's made
explicit.
sergei-maertens added a commit that referenced this issue Mar 25, 2024
From zgw api group instance to form backend configuration, making
the fields explicit.
sergei-maertens added a commit that referenced this issue Mar 25, 2024
Instead, make the fields required on the options serializer, ensuring
they're specified for each registration backend.

The previous commit handles the data migration for the instances
without explicit configuration.
sergei-maertens added a commit that referenced this issue Mar 26, 2024
Instead, make the fields required on the options serializer, ensuring
they're specified for each registration backend.

The previous commit handles the data migration for the instances
without explicit configuration.
sergei-maertens added a commit that referenced this issue Mar 26, 2024
Dropping gemma-zds-client means that we can't use any of its
API anymore.
sergei-maertens added a commit that referenced this issue Mar 26, 2024
Dropping gemma-zds-client means that we can't use any of its
API anymore.
sergei-maertens added a commit that referenced this issue Mar 26, 2024
Dropping gemma-zds-client means that we can't use any of its
API anymore.
sergei-maertens added a commit that referenced this issue Mar 26, 2024
Configuration of the fields (defaults) from zgw api group needs to be
stored on the registration backend options so that it's made
explicit.
sergei-maertens added a commit that referenced this issue Mar 26, 2024
From zgw api group instance to form backend configuration, making
the fields explicit.
sergei-maertens added a commit that referenced this issue Mar 26, 2024
Instead, make the fields required on the options serializer, ensuring
they're specified for each registration backend.

The previous commit handles the data migration for the instances
without explicit configuration.
sergei-maertens added a commit that referenced this issue Mar 26, 2024
Dropping gemma-zds-client means that we can't use any of its
API anymore.
sergei-maertens added a commit that referenced this issue Mar 26, 2024
Which drops gemma-zds-client as dependency.
sergei-maertens added a commit that referenced this issue Mar 26, 2024
The import was a left-over import that didn't have any effect.
sergei-maertens added a commit that referenced this issue Mar 26, 2024
So that this can be used in VCR tests.
sergei-maertens added a commit that referenced this issue Mar 27, 2024
Discussed with the team on Slack, extensive input validation
where relations between configuration aspects are verified
for consistency and integrity is required, but only during
configuration of the form.

At registration time itself, only the validations that don't
touch external services are performed, so that:

* tests are simpler to write without having to set up mocks
  or VCR, distracting from the actual tested behaviour
* performance during registration is not affected because
  of additional IO. A validation error on this aspect
  would manifest as a runtime error anyway, which is the
  same outcome as the remote API not accepting the
  configured options.
sergei-maertens added a commit that referenced this issue Mar 28, 2024
Discussed with the team on Slack, extensive input validation
where relations between configuration aspects are verified
for consistency and integrity is required, but only during
configuration of the form.

At registration time itself, only the validations that don't
touch external services are performed, so that:

* tests are simpler to write without having to set up mocks
  or VCR, distracting from the actual tested behaviour
* performance during registration is not affected because
  of additional IO. A validation error on this aspect
  would manifest as a runtime error anyway, which is the
  same outcome as the remote API not accepting the
  configured options.
sergei-maertens added a commit that referenced this issue Mar 28, 2024
The updated validation would require adding more mocks to the existing
tests, or instead, we can extend the fixture and use VCR for the Open
Zaak API interaction.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant