Categories:
Hot swapping processes in Aura distributed architecture
Guidelines to execute modifications in Aura distributed architecture through a hot swapping process
Introduction
Constructors can add, delete of modify a skill through a hot swapping process, without affecting other skills, through the aura-configuration-api.
Through this process, aura-groot can be modified to route to a new skill or delete from its routing tables other skills if constructors do not want to send requests to them.
Guidelines
Add a new skill
-
Deploy a new skill in your own deployment site.
-
Prepare your channel:
- (Optional) If your skill is serving a new channel, add the channel to the aura-configuration-api.
- (Optional) If your skill is serving an already existing channel that is not handled by any skill, nothing is needed.
- (Optional) If your skill is serving an already existing channel that is handled by another skill, delete the channel from the current skill configuration aura-configuration-api, launching a
PATCHrequest.
-
Prepare the
POSTrequest to the aura-configuration-api in order to add the skill. -
Send the request to the aura-configuration-api to add the skill.
-
After the request is processed, aura-groot automatically loads the new skill and starts routing requests to it.
Delete an existing skill
-
Prepare the
DELETErequest to the aura-configuration-api to delete the skill. -
Send the request to the aura-configuration-api to delete the skill.
-
After the request is processed, aura-groot automatically removes the deleted skill and no longer routes requests to it.
-
(Optional) If your skill is serving a dedicated channel that is no longer needed, remove the channel from the aura-configuration-api.
-
At this point, the skill can be undeployed from your deployment site.