Support sharing definitions between repos with different languages/package managers about contextive

[lukespice]

Thanks for this, they are interesting options and I agree with the pros and cons assessments.

I really like the idea of self published or hosted like a swagger file as it could be a way to share the content with stake holders / domain experts who don't have access to the source code repository. Although I definitely agree with both of those cons, especially that there may be sensible objections to publicly exposing the details of your core domains.

Raw URL or cloning the repo both seem like sensible options and seem fairly equivalent usability. I would prefer whichever has the least friction. My current workplace at least all use SSH keys for Bitbucket connectivity as this is required for private Go packages so that shouldn't be painful for us.

[bluecitylights]

I am doing this self published for my integration events. The page describes both the external events the service subscribes to as well as the outgoing events. Next to our swagger.

[chrissimon-au]

Thanks for the info @bluecitylights - can you share a few more details on how/where you are publishing the files? And are you pulling them down into other repositories so contextive can work in those repositories?

Would you like contextive to offer more native/built in support for that pattern, or is it leveraging other things you're doing outside contextive (in which case it might make sense for contextive to be ignorant/agnostic as to how you're doing it...)