Owner: Architect:

Francesco Ilario

Story (Required)

As a Primaza Administrator, I would like to have an Application Agent so that Primaza can perform Service Claiming and Service Binding in application namespaces

Background (Required)

As described in the Primaza architecture document, application binding will be eventually performed by slim agents deployed into application namespaces.
Also, the agent would react to in-namespace creation of Service Claims, forwarding them to Primaza.

Look to related stories for Service Agent deployment development.

Glossary

See glossary in architecture document

Out of scope

• Service Claiming
• Service Binding
• Push agents/controllers to the clusters

In Scope

• scaffold application agent

Approach(Required)

Create a folder for the agent, like cmd/applicationagent with Application Agent main.
Makefile should also be updated with needed rules for building and deploying the Application Agent.

Demo requirements(Required)

NA

Dependencies

NA

Edge Case

NA

BDD Tests

You can find BDD Test specification for this story at in the Github Issue linked to this story

Acceptance Criteria

• Development
  Scaffold the necessary infrastructure for building the agent.

• QE
  Build and deploy rules in Makefile are updated to support the Application Agent build

• Docs
  There is a page in our docs dedicated to explaining what an Application Agent is
  Update architecture document with any changes while implementing/
  There is a link in our main readme to the Application Agent page

INVEST Checklist

Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated

Legend

Unknown
Verified
Unsatisfied