-
Notifications
You must be signed in to change notification settings - Fork 26
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
Deprecations to remove in 3.0 #3283
Comments
There is also the "old" cosign, but I don't know if we want to remove it afterall |
Good shout - we can discuss that at some point. I think it depends a bit on who's actually using it? |
@vaszig you can pick up removing the old appointments integration |
Per the deprecation warning we drop support for exports containing the legacy translation store.
Per the deprecation warning we drop support for exports containing the legacy translation store.
@sergei-maertens the only field that is nullable from what I can see is Should this be required? |
Per the deprecation warning we drop support for exports containing the legacy translation store.
This component never made sense, it was only added reluctantly because the original programme of requirements specified it. Passwords being stored in plain text are a terrible, terrible idea. Nobody should have every actually used this in a real form.
This component never made sense, it was only added reluctantly because the original programme of requirements specified it. Passwords being stored in plain text are a terrible, terrible idea. Nobody should have every actually used this in a real form.
The shape of data that we store was badly documented, not in the least because we barely had any idea what kind of information we receive. Since Open Forms 2.7.0 it has been fleshed out what the mandata context looks like, and properly implemented backed by a proposal for a standard which is implemented all the way to Open Zaak to try out. This legacy context is now being removed in favour of the new way to track and expose the mandata context.
With Open Forms 3.0, we can make the breaking change of updating the default. The new OIDC API endpoints all point to a single callback URL, so it means less configuration overhead on the identity provider side. The breaking change means that the new URI's must be added to the allowlist of the identity provider. The new endpoint is '/auth/oidc/callback/', and it applies to all OIDC configuration flavours.
With Open Forms 3.0, we can make the breaking change of updating the default. The new OIDC API endpoints all point to a single callback URL, so it means less configuration overhead on the identity provider side. The breaking change means that the new URI's must be added to the allowlist of the identity provider. The new endpoint is '/auth/oidc/callback/', and it applies to all OIDC configuration flavours.
Providing both the used_in and is_reusable filter parameters no longer returns records that match either condition, instead it applies the default AND behaviour.
Some older endpoints used underscores, but the majority of endpoints use kebab-case to separate words, so now everything is normalized. This requires a PR to the SDK to handle the changes, as no redirects are being set up. All of these endpoints are private API.
…casing in the API endpoints Switched from underscore to kebab case, so hardcoded endpoints need to be adapted.
Catalogi and Documents API are optional, but the objecttypes and objects API services are not. These fields were null because the model was originally a django-solo singleton model which must be able to be created without any services existing prior. A check script is added to prevent being stuck in half-migrated upgrades.
Left-overs from a django-solo model too (see previous commit), these fields really cannot be empty to do anything useful. This properly sets up the required constraints at the database level and removes confusion in the application code.
Catalogi and Documents API are optional, but the objecttypes and objects API services are not. These fields were null because the model was originally a django-solo singleton model which must be able to be created without any services existing prior. A check script is added to prevent being stuck in half-migrated upgrades.
Left-overs from a django-solo model too (see previous commit), these fields really cannot be empty to do anything useful. This properly sets up the required constraints at the database level and removes confusion in the application code.
Catalogi and Documents API are optional, but the objecttypes and objects API services are not. These fields were null because the model was originally a django-solo singleton model which must be able to be created without any services existing prior. A check script is added to prevent being stuck in half-migrated upgrades.
Left-overs from a django-solo model too (see previous commit), these fields really cannot be empty to do anything useful. This properly sets up the required constraints at the database level and removes confusion in the application code.
Catalogi and Documents API are optional, but the objecttypes and objects API services are not. These fields were null because the model was originally a django-solo singleton model which must be able to be created without any services existing prior. A check script is added to prevent being stuck in half-migrated upgrades.
Left-overs from a django-solo model too (see previous commit), these fields really cannot be empty to do anything useful. This properly sets up the required constraints at the database level and removes confusion in the application code.
With Open Forms 3.0, we can make the breaking change of updating the default. The new OIDC API endpoints all point to a single callback URL, so it means less configuration overhead on the identity provider side. The breaking change means that the new URI's must be added to the allowlist of the identity provider. The new endpoint is '/auth/oidc/callback/', and it applies to all OIDC configuration flavours.
…gration-procedure 📝 [#3283] Document registration backend migration procedure
With Open Forms 3.0, we can make the breaking change of updating the default. The new OIDC API endpoints all point to a single callback URL, so it means less configuration overhead on the identity provider side. The breaking change means that the new URI's must be added to the allowlist of the identity provider. The new endpoint is '/auth/oidc/callback/', and it applies to all OIDC configuration flavours.
A list of breaking changes to make when we get to version 3.0
CTRL + F on
DeprecationWarning
in the backend to find more.INVESTIGATE: can we keep existing endpoints on /api/v2/ and new ones to /api/v3/ so we don't have to move everything at once?Resolving by marking most of the API private APIAppointments [#3283] Remove oldstyle appointments flow #4872
appointments.utils
Formio
fd_translations_converter
module (this will affect exports < 3.0 that have legacy translations) 💥 Drop legacy formio translation converter #4828Form design
formStepUuid
💥 Remove conversion of form step URL to form step UUID #4892FormDefinitionSerializer.name
readOnly
(name is set via translations) @stevenbal_data
model fieldopen-forms/src/openforms/submissions/models/submission_step.py
Line 102 in 8f7b003
Styling/NL DS
of-page-header-*
andof-page-footer-*
in favour ofutrecht-page-header-*
andutrecht-page-footer-*
tokens @robinmolencomponents/_page-header.scss
components/_page-footer.scss
Registration:
Remove document type conversion hook (if it exists)Remove documenttype URLs - auto migrate where possible (management command to be added in 2.8.x?)Authentication
Switch DigiD/eHerkenning OIDC from Lax to Strict mode #4890Misc
/api/v2/location/get-street-name-and-city
in favour of/api/v2/geo/address-autocomplete
@robinmolenTemporaryFileUpload.submission
FK @sergei-maertensThe text was updated successfully, but these errors were encountered: