Bots with CI/CD
# supportc
Charlie from Imagine
09/14/2023, 9:22 PMIs there a way to deploy all bots in a given directory? I would like to create a CI/CD process that deploys our bots to our Medplum projects in a pipeline when we merge our PRs.
r
rahul1
09/14/2023, 9:28 PMHi @Charlie from Imagine - check out our "Bots in Production" doc to see how to integrate Bots into your SDLC: https://www.medplum.com/docs/bots/bots-in-production#deploying-your-bot
rahul1
09/14/2023, 9:29 PMYou can use the medplum cli (
medplum bot deployc
Charlie from Imagine
09/14/2023, 9:29 PMYeah, those docs are dealing with 1 bot at a time.
r
rahul1
09/14/2023, 9:30 PMWe don't have a way to deploy by-folder just yet, but we do support wildcard for deploy multiple bots: https://www.medplum.com/docs/bots/bots-in-production#deploying-your-bot
c
Charlie from Imagine
09/14/2023, 9:30 PMOhhhh
Charlie from Imagine
09/14/2023, 9:30 PMI completely missed that wildcard bit
Charlie from Imagine
09/14/2023, 9:30 PMThats exactly what we need!
r
rahul1
09/14/2023, 9:31 PMSo if you named all your bots in
medplum.config.json[botname]-productionc
Charlie from Imagine
09/14/2023, 9:31 PMYep, this is better than by dir
Charlie from Imagine
09/14/2023, 9:31 PMThanks Rahul!
Charlie from Imagine
09/14/2023, 9:55 PM@rahul1 is there a way to manager subscriptions with CI/CD too?
r
rahul1
09/15/2023, 3:42 AMi.e add / remove a subscription to the Bots from CI/CD?
There isn't a 1-command "deploy" option, but you can use the medplum CLI to create/update subsciptions, as they are just another resource: https://www.medplum.com/docs/cli#post
c
Charlie from Imagine
09/20/2023, 5:49 PM@rahul1 when deploying from automation, should you have to run
medplum loginr
rahul1
09/20/2023, 5:51 PMYou should not need to you. You can create a
ClientApplicationrahul1
09/20/2023, 5:51 PMLet me get that info to you
c
Charlie from Imagine
09/20/2023, 5:51 PMHmmm I saw that in the bot in production docs, but when testing locally it still sent me to a browser.
Charlie from Imagine
09/20/2023, 5:52 PMMaybe I didnt set things right 🤔
r
rahul1
09/20/2023, 6:40 PMIf those env vars are set, hopefully shouldn't need to run
loginrahul1
09/20/2023, 6:40 PMlet me know if that isn't wokring
rahul1
09/20/2023, 7:10 PMMEDPLUM_CLIENT_IDMEDPLUM_CLIENT_SECRETrahul1
09/20/2023, 7:10 PMPlease let me know if this workflow is not working
rahul1
09/20/2023, 9:34 PMYou could also use the command line params as well
Copy code
medplum deploy-bot --help
Usage: medplum deploy-bot [options] <botName>
Deploy the bot to AWS
Options:
--client-id <clientId> FHIR server client id
--client-secret <clientSecret> FHIR server client secret
--base-url <baseUrl> FHIR server base url
--token-url <tokenUrl> FHIR server token url
--authorize-url <authorizeUrl> FHIR server authorize url
--fhir-url-path <fhirUrlPath> FHIR server url path
--scope <scope> JWT scope
--access-token <accessToken> Access token for token exchange authentication
--callback-url <callbackUrl> Callback URL for authorization code flow
--subject <subject> Subject for JWT authentication
--audience <audience> Audience for JWT authentication
--issuer, <issuer> Issuer for JWT authentication
--private-key-path <privateKeyPath> Private key path for JWT assertion
--audience <audience> Audience for JWT assertion
-p, --profile <profile> Profile name
--auth-type <authType> Type of authentication (choices: "basic", "client-credentials", "authorization-code", "jwt-bearer", "token-exchange", "jwt-assertion")
-h, --help display help for command161 Views