Break out golang coinstacks #955
Description
Overview
Now that we have crossed the bridge of incompatible direct dependencies for our golang coinstacks, we will need to find a way to break out these coinstacks, while ideally still leveraging as much shared code as we can moving forward.
References and additional details
I spiked in the past with go workspaces and various ways to try and manage this situation within the monorepo context, but was unsuccessful. Would still be worth looking at the current available options again for posterity
Acceptance Criteria
- Ability to maintain disparate golang coinstacks without requiring a long running "forked" feature branch
- Hope to reuse as much common logic as is feasible
- Would be idea to have the outcome still be able to be used by unchained directly to retain a single deployment pipeline and not need to also package up all of the infra on top for reusability outside of unchained
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response