Create harmony_composer initial #58
No reviewers
Labels
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: NationTech/harmony#58
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "harmony_ci_cli"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I'm thinking so many things that I'm not sure what to think 😆
One one hand, there are many interesting ideas there and I'm really curious to see how it will evolve.
On the other hand, I feel like it would be better to start smaller and simpler, with one very clear feature to implement for our customer. Implement one full simple feature instead of planning all the future features before even having one done. Working too wide and not following YAGNI enough is usually how you end up with an architecture that does not work/scales well because we haven't figured out yet how it actually works.
So I guess that at this point we can keep it like this as a starting point, but now we should focus on end-to-end integration of the first feature. I guess that would be creating a simple way to use this CLI to detect an existing harmony configuration and execute it without providing more advanced functionnality at this point, just basic execution of whatever is already written in the harmony code.
@ -11,3 +11,3 @@
"opnsense-config-xml",
"harmony_cli",
"k3d",
"k3d", "harmony_composer",
Format
d05375f5ee
to9c29e92a46
0da10a1ee2
to3f69edf059
dind
(Docker-in-Docker supporting) runners