[admin/api] Make batch user creation organization field readonly #609 #618
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR makes the organization field readonly for existing RadiusBatch objects in both the admin interface and REST API, addressing issue #609.
When the batch user creation object has been created, there's no point in changing the organization field, and this change disallows modification to maintain data integrity.
Changes
Admin Interface
RadiusBatchAdmin.get_readonly_fields()
to includeorganization
field for existing objectsREST API
RadiusBatchUpdateSerializer
with organization as readonly fieldBatchUpdateView
for handling batch detail operations (retrieve/update)/radius/batch/<uuid:pk>/
)Testing
test_radiusbatch_organization_readonly_for_existing_objects
test_radiusbatch_organization_editable_for_new_objects
test_batch_update_organization_readonly
test_batch_retrieve_and_update_api
test_batch_update_permissions
Checklist
Fixes #609