fix: add recording-name api key endpoint; appauth url fix #8081
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.
The main fix here is to register the
/api/meeting/session/recording-name
endpoint as valid forPersonalApiKey
endpoints.Along the way, found that tests were not validating the
PersonalApiKey
instances they were generating, so this updates thePersonalApiKeyFactory
to do that validation and replaces calls toPersonalApiKey.objects.create()
with the factory.This conversion revealed a minor bug in the URL pattern for
/api/appauth/
which is also fixed.