As of May 2, 2019 (AAF 2.1.12-SNAPSHOT-latest, dbc-client 1.0.8-STAGING-latest, dmaap-bc 1.1.4-STAGING-latest, dmaap-mr 1.1.13)

All the old AAF dependencies have been resolved in 2.1.12-SNAPSHOT.  However, a minor error has been introduced.

Known Issues:

1. the permissions for the message-router identity are not correct.  Symptom is that client authorization fails.  This is why mirrormaker pod is not able to start.
2. some aaf pods are not reaching a ready status.  This can be ignored as they are not utilized.  Pods are "aaf-sms" and "aaf-sms-preload".

Resolution:

create override file with contents:

#################################################################
# Enable/disable and configure helm charts (ie. applications)
# to customize the ONAP deployment.
#################################################################
aaf:
  enabled: true
dmaap:
  enabled: true
message-router:
  enabled: true
dmaap-bc:
  enabled: true
dmaap-dr-node:
  enabled: false
dmaap-dr-prov:
  enabled: false

1. Deploy AAF separately first.
   1. helm install --debug local/aaf -n central-aaf --namespace onap -f ~/dgl_overrides.yaml --timeout 900
2. In AAF GUI add:

role user add org.onap.dmaap.mr.admin dmaapmr@mr.dmaap.onap.org

       3. Deploy dmaap.

helm install --debug local/dmaap -n central-dmaap --namespace onap -f ~/dgl_overrides.yaml --timeout 900