Thomi,
As we have been discussing, I don't much benefit in making input/output queues configurable when both config & code are equally static/immutable to us, specially while we can't find a way to materialise & relate config-file to deployment (1:1).
We talked about this in the standup and I've tried to capture most of our ideas in https://trello.com/c/FuwQzdA4/22-1-core-result-checker-publish-to-pm-results.
« Back to merge proposal
Thomi,
As we have been discussing, I don't much benefit in making input/output queues configurable when both config & code are equally static/immutable to us, specially while we can't find a way to materialise & relate config-file to deployment (1:1).
We talked about this in the standup and I've tried to capture most of our ideas in https:/ /trello. com/c/FuwQzdA4/ 22-1-core- result- checker- publish- to-pm-results.