Value Statement

GH (or Fabric) will have to be extended for O-RAN, Flight control etc.
So we will have to work with fabric team to decide what is the optimal to way to extend what they do — without needing to go back to them all the time.The above exercise - just focused on ACM needs will serve as a good template for future needs.
If this was OOPs, we would use inheritance, sub classing etc.... But what do we do in this case of DB? (I know postgres can extend tables - but may be we do not use that)......
This experiment will help us to determine this.

Definition of Done for Engineering Story Owner (Checklist)

• Connect the grafana to inventory DB
• list the gaps in order to support our grafana dashboard

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.