Some remaining TODOs that I don't believe are blockers:
[x] production and staging files have some duplication (not a whole lot since most env vars end up having different references anyways). ~The override policy method is kind of pointless here because the production and staging manifests have to be separate files anyway.~ Using the topology policy and two workflow steps they can now be in the same file
[ ] When a new image is pushed because of a code change, I'm not sure if flux will realize and re-deploy, because I think only manifest changes cause re-deploy. The optimal solution to this is to have flux/kubevela build images as part of the deploy workflow, but a temporary solution is to trigger the deploy manually after images are pushed.
Pre-submit checklist:
Branch
[ ] Tests are provided (if possible)
[ ] Commit sequence broadly makes sense
[ ] Key commits have useful messages
[ ] Relevant tickets are mentioned in commit messages
[ ] Formatting, materialized Nix files, PNG optimization, etc. are updated
The application is being synced here https://vela.scdev.aws.iohkdev.io/applications/marlowe-playground-repo/config. The status of all components can also be viewed when clicking on marlowe-staging at the top.
Some remaining TODOs that I don't believe are blockers:
Pre-submit checklist: