[APP 2911] Step Towards Removal of Legacy Robot API Keys #4374
+28
−71
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
viambot
added
the
safe to test
viambot
added
safe to test
bashar-515
changed the title
viambot
added
safe to test
bashar-515
force-pushed
the
APP-2911
branch
from
3fb0c62
to
8c8660a
Compare
viambot
added
safe to test
bashar-515
force-pushed
the
APP-2911
branch
from
9f5ea2a
to
8c8660a
Compare
viambot
added
safe to test
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR almost fully phases out the use of legacy robot API keys by taking out most of the code that explicitly parses for them via a "key" field in the API key handler config to become solely reliant on {"API_KEY_ID": "API_KEY"} (i.e., new API key). Some code still remains to account for a "keys" field - this is the only remaining artifact of legacy keys. Currently, the "keys" field maps to a list of the ID's of the robot's API keys - so it's redundant. It's necessary, though, for backwards compatibility. RDK currently requires the "keys" field, so the phasing out of legacy keys in app hasn't allowed for the removal of "keys" as a field. Also in this PR is the reconfiguration of various tests in order to account for the change in APP slightly affecting the structure of the API key auth config.
Testing: local testing suites pass and my dummy local robot as able to connect manually.