Automated publishing of Meshery core definitions

[leecalcote]

          Is there a conjoining PR in meshery/meshery to delete these definitions?

Is the registry model generator configured to source components from meshery/schemas?

Or is there workflow that needs to populate meshery/meshery with updates to these schemas? // @MUzairS15

Originally posted by @leecalcote in #58 (comment)

[leecalcote]

Is this needed? #40 // @Yashsharma1911

[leecalcote]

@Yashsharma1911 @MUzairS15 has this been implemented?

[leecalcote]

If v1beta1 of components is ready to release, new definitions in #73 will have already been created and pushed, correct?

[MUzairS15]

Yes we are referencing defs in schemas repository and automatically sync those to meshery repo.

Release of meshery will also necessitate release of schemas with new v1beta1 defs. Those will be updated.

[leecalcote]

Thanks for confirming. I tend to think of the direction of our development differently. I think that being schema to definition to declaration to instance is the way that our development should go.

[MUzairS15]

Yes I agree with the order of development. Because for core models are curated by us, we need to define it somewhere, instead of skipping the first step (starting from defs) we can start from the schema.
We will need to define kind for these comps (similarly to that of CRD)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.