You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 22, 2024. It is now read-only.
1A.2 make sure the schema has no conflict with latest version of uploaded schema. Assuming this will be the version deployed in the cluster.
1B. When deploy app, is it necessary to check? after all has to be done with buildApp. But what about we try to deploy a rollback or anything of that sort. Would be still compatible? I think so
Starting with remote Schemas
2A. When writing the app. So they need a way to download it or should be always part of the source code? tempted for the later to avoid problems.1
2B. When buildApp same as 1A
problems:
if from one workstation that access to the schema uses style 2 and from the next workstation there's no access to the registry -> always add schemas in local?
The text was updated successfully, but these errors were encountered:
the UX
the developer may want to
Starting with local schemas
Starting with remote Schemas
problems:
The text was updated successfully, but these errors were encountered: