bcgov / traction

Traction is designed with an API-first architecture layered on top of Hyperledger Aries Cloud Agent Python (ACA-Py) and streamlines the process of sending and receiving digital credentials for governments and organizations.
https://digital.gov.bc.ca/digital-trust/tools/traction/
Apache License 2.0
52 stars 48 forks source link

Unable to config Admin name and key for innkeeper via deploying using helmcharts #1310

Closed shanmukh-777 closed 2 weeks ago

shanmukh-777 commented 1 month ago

Hi, Recently i using traction with docker .But when i tried to deploy traction in kubernetes via helm charts , i am unable to find admin name,key for innkeeper or config them under plugin-config.yaml of acapy inside values.yaml .but its of no use,Can some one help me about which step i am doing wrong and also how to config innkeeper to use custom admin name and key

Below is the acapy section of values.yaml i am using ,

@section Acapy Configuration

acapy:

image: repository: ghcr.io/bcgov/traction-plugins-acapy pullPolicy: IfNotPresent pullSecrets: [] tag: "" serviceAccount: create: false annotations: {} automountServiceAccountToken: true name: "" replicaCount: 1

AcaPy Autoscaling configuration

autoscaling: enabled: false minReplicas: 1 maxReplicas: 3 targetCPUUtilizationPercentage: 80 targetMemoryUtilizationPercentage: 80 stabilizationWindowSeconds: 300

labelOverride: ""

@section Acapy configuration file

@param acapy.argfile.yml.auto-accept-invites Automatically accept invites without firing a webhook event or waiting for an admin request. Default: false.

argfile.yml: auto-accept-invites: true auto-accept-requests: true auto-create-revocation-transactions: true auto-ping-connection: true auto-promote-author-did: true auto-provision: true auto-request-endorsement: true auto-respond-credential-offer: false auto-respond-credential-proposal: false auto-respond-credential-request: true auto-respond-messages: true auto-respond-presentation-proposal: true auto-respond-presentation-request: false auto-store-credential: true auto-verify-presentation: true auto-write-transactions: true emit-new-didcomm-mime-type: true emit-new-didcomm-prefix: true endorser-alias: endorser endorser-protocol-role: author genesis-transactions-list: /home/aries/ledgers.yml label: '{{ include "acapy.label" .}}' log-level: info monitor-ping: true monitor-revocation-notification: true multitenant-admin: true multitenant: true notify-revocation: true preserve-exchange-records: true public-invites: true read-only-ledger: false tails-server-base-url: https://tails-test.vonx.io tails-server-upload-url: https://tails-test.vonx.io wallet-name: askar-wallet wallet-storage-type: postgres_storage wallet-type: askar

Acapy multiledger configuration file

param acapy.ledgers.yml [object] YAML configuration for connecting to multiple HyperLedger

ledgers.yml:

shanmukh-777 commented 2 weeks ago

I got my problem solved,its not about configuration os issuer,but to expose the tenant-proxy via nodeport because to make it accessable to tenant-ui outside kubernetes cluster