You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ccloud cli can be installed in a thin deployment startup image and have credentials passed in via secret. Either a ~/.netrc file or pass into ccloud login invocation.
These should only happen on dev/stage since topic state on prod cannot just be wiped.
clinvar-raw: delete/recreate clinvar-raw topic before launching deployment
clinvar-combiner: delete/recreate clinvar-combined topic before launching deployment
The text was updated successfully, but these errors were encountered:
theferrit32
changed the title
Tie confluent cloud topic state management into dev/stage deployments
Tie confluent cloud topic state management into dev/stage clinvar-streams deployments
Apr 5, 2021
It looks like the only way to authenticate to the ccloud CLI is through Confluent admin accounts, which are email-based. I don't see a way to authenticate to it using a Confluent cluster service account. We could potentially use the clingen devs google group account. Or create another account if that one is too broad use.
The java org.kafka API for managing topics seems a little not-straightforward. The confluent kafka library in python has an admin client that can do it
ccloud
cli can be installed in a thin deployment startup image and have credentials passed in via secret. Either a~/.netrc
file or pass intoccloud login
invocation.These should only happen on dev/stage since topic state on prod cannot just be wiped.
clinvar-raw
topic before launching deploymentclinvar-combined
topic before launching deploymentThe text was updated successfully, but these errors were encountered: