Add reset endpoints for the auth, todos and users to be reconfigured at runtime #8
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
The change adds new endpoints for changing the authentication and data setup dynamically at runtime.
Why: We need to create the API as a sidecar to enable it in any base task we want, and since we don't have shared memory space for sidecars, it won't be possible to load and start the api in the setup.sh. In order to create sidecar, and still be able to provide custom initial todos, and authentication method, we need new endpoints to accommodate that.
Changes
/auth/reset
endpoint that takes the auth method and key in a POST request and resets the app with the new configuration./auth/reset-users
endpoint that takes users json as a file and resets the app./todos/reset
endpoint that takes todos json as a file and resets the app with new todo items.NOTE: The endpoints are expected to be used only in
setup.sh
, but we cannot enforce that – so I'm open to suggestions. (we could have rate limit on those endpoints potentially)