Fix Agent Registration Behavior #319
Merged
+45
−40
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.
Summary
This pull request addresses two issues:
Changes
AgentInfo
component to delay database writes until registration is confirmed.Save()
method to persist data only after successful registration.Modified the expected status code for registration responses from
200
to201
.Tests
Set()
andSave()
.Save()
is called.201
status code as a success indicator.201
and does not fail the registration process.201
responses result in successful registration.Important
In this change, we simplify the
RegistrationTestSuccessWithEmptyKey
test, since this test makes the agent produce a random key. Since persistence is removed, the mock does not have access to the new key. However, the persistence behavior ofAgentRegistration
is checked inRegistrationSuccess
.Manual testing
Registration failure
sqlite3 agent_info.db 'select * from agent_info'
Registration success
sqlite3 agent_info.db 'select * from agent_info'