Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consume channels from other specs using reference #59

Open
big-andy-coates opened this issue Feb 2, 2023 · 1 comment
Open

Consume channels from other specs using reference #59

big-andy-coates opened this issue Feb 2, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@big-andy-coates
Copy link
Member

big-andy-coates commented Feb 2, 2023

Problem:
Currently 'consume' channels are required to put in the full entry of the other spec - this means duplication of schema refs, key location etc. ideally a reference approach ( some.other.domain._public.events: consume: etc) should be enough.

Implementation:
At runtime/parse-time, Specmesh will use the reference to complete/hydrate the spec using the reference. Of which itself will be publish to the same location/git etc (i.e. using git master as a registry)


Need to work out the story / workflow for validating multiple domains with specs in different repos.

For example, if I remove a public topic, or a grant on a protected topic, in one repo by mistake, the downstream domain need to detect this. Ideally, this is caught as early as possible... e.g. in the build pipeline.

Thoughts:
Maybe we can reference the upstream specs straight out of the main branch of GitHub?
Then users could have periodic builds (nightly or what ever) that check that no changes upstream has broken the current repo.

Later we'll want to think about how to toolify this so that the up stream repo user is notified when removing a topic / grant that still in use...

@bluemonk3y
Copy link
Collaborator

Ideally using a reference approach where specmesh uses a registry or master-git location to resolve the entry

(i.e. some.other.domain._public.topc -> consume - ref: version-1)

no other details required. i.e. act like a symbolic link

@bluemonk3y bluemonk3y changed the title Multi-domain SDLC Consume channels from other specs using reference Jul 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Todo
Development

No branches or pull requests

2 participants