Hello team, we have been playing around a bit with the self hosted option, and we found some roadblocks while setting up a CI/CD deployment process. 1. The big one is that a couple of script depend on user input, which for us (using CircleCI) was impossible to bypass. There are 2 scripts that have that logic: 1.A.

init

(https://github.com/medplum/medplum/blob/main/packages/cli/src/aws/init.ts) --> I think it's going to be hard to automate 1.B.

update-config

(https://github.com/medplum/medplum/blob/main/packages/cli/src/aws/update-config.ts) --> I made a PR to fix this one (https://github.com/medplum/medplum/issues/4600), but I don't know how to continue after creating the issue and my fork. 2. Thinking about the

init

script, we have a couple of questions: 2.A. Why is the signing key created in this script instead of being part of the CDK? 2.B. If a valid config json is created by hand, could we skip running it and call

update-config

instead? Thanks in advance

Hi @infinnitum for #2, thanks for the issue. To push the pull request to our main repo, you can follow the instructions here: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork

Thanks for the link, here is the PR: https://github.com/medplum/medplum/pull/4625