cht-core
cht-core copied to clipboard
medic
feat(#8551): removes python from cht-deploy and some bug fixes
Description
Handles the following tickets:
#8551 Remove python - establishing feature parity. No major refactoring. #8604 Catch Missing Values #8605 Show URL when done execution #8608 Add a get-all-logs troubleshooting command
Code review checklist
- [ ] Readable: Concise, well named, follows the style guide, documented if necessary.
- [ ] Documented: Configuration and user documentation on cht-docs
- [ ] Backwards compatible: Works with existing data and configuration or includes a migration. Any breaking changes documented in the release notes.
Compose URLs
If Build CI hasn't passed, these may 404:
License
The software is provided under AGPL-3.0. Contributions to this project are accepted under the same license.
Comments addressed. A few tests added and build is passing. Also integrated with CI. This puts us in a better spot that we can iterate on.
@nydr yes, I've actually already published this to npm. https://www.npmjs.com/package/@medic/cht-deploy. It can be run via npx @medic/cht-deploy -f <path-to-your-yaml>
@henokgetachew @mrjones-plip I know it's been busy lately. Is there anything we can do to help this PR?
We are currently pulling from a commit (4760b5d30017a86d90ae95b1d570ba9ed6d053dc) to keep using EKS instances. Especially to verify issues during releases in CHT, so fixing and merging this PR will help the release managers to not rediscover the same issue error: InvalidImageName in the upgrade service.
I can confirm that this worked for me when testing out the upgrade to release 4.10.0 when the demo instance was not working.
This is actually on my plan for today. Until the merge by the way, you should be able to use:
npx @medic/cht-deploy@latest -f <your-yaml.yaml>
Thanks for the push @latin-panda ! Much appreciated.
We are currently pulling from a commit (4760b5d30017a86d90ae95b1d570ba9ed6d053dc) to keep using EKS instances.
At the point this is true, we just need to merge the branch. If everyone is using the branch as production, there's simply no reason to not merge it. We can create new tickets for work that wasn't completed.
Great to see you making some commits on this Henok! Given this is in production use already, we should commit to merging this either way before week's end. I'm available to help as needed!!
