I like the idea of deployable projects. If you took a zone to the next step where it would acually live in a separate config that you could deploy, start and stop independently of other 'zones' it would make SCM, team development and deployment much easier.
I second this. A config that I can check in with a solution that only contains topics/parties/pipelines that are applicable to that solution would be great. If, after deployment, they can be started/stopped independently would be great but allowing Neuron to "merge" in the config would be fine too.
I definitely vote for the ideas from Kris and Ryan about deployable solutions. Somehow to export the relevant parts for the solution from the development/test config into a package that can be imported into the config at next stage (qa/prod whatever).
Also I'd like to see the Service Engine be released. The betas looked interesting but of course it has to be stable for release.
And then stay focused on how Neuron fits into the MS stack with Oslo, Dublin etc.
Is it possible to create a custom OAuth provider? Specifically, we are working with Cisco (https://cloudsso.cisco.com/as/token.oauth2).We have a requirement to integrate with a Cisco soap server which uses OAuth2 for authentication. We are using a Service Connector to send a message to the SOAP service, but we need to write custom code in a business process to authenticate with their Cisco OAuth provider. We saw that Neuron supports…See More
Hi, We are using 3.5 for our application and I am trying to containerise it for our integration tests. Building and deploying VM's as this is very time consuming to build and deploy.So I have decided that I to go down docker; everything in our stack has migrated nicely except Neuron. The first issue was that I needed a later version of the 2016 image or 2019 image from MS which I have. I have managed to install MSMQ on it as well. But when I try to run a silent install everything runs. But…See More