-
Notifications
You must be signed in to change notification settings - Fork 200
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
Remove synapse-configs folder #136
Labels
Comments
IMO it is better to keep the synapse folder since users can add individual files (proxies, sequences etc) instead of carbon apps. It can help users for quick testing. Therefore I think we should keep it |
For quick testing they can use Tooling debugging functionality or Unit Testing Framework at the development time in the tooling itself. |
senthuran16
pushed a commit
to senthuran16/micro-integrator
that referenced
this issue
Nov 1, 2021
Change the query to include all the column names
senthuran16
pushed a commit
to senthuran16/micro-integrator
that referenced
this issue
Nov 1, 2021
senthuran16
pushed a commit
to senthuran16/micro-integrator
that referenced
this issue
Nov 1, 2021
… development iteration
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
We deploy to micro integrator via EI Tooling. EI tooling always creates a CAPP which is deployable to Micro Integrator.
As there is no Web UI or any place we can create and deploy individual artifacts. Thus better to remove
synapse-configs
folder altogether and keepcarbonapps
folder only.There are some more deployment specific folders like
axis2modules
,axis2services
etc which is not relevant to MI usecase.The text was updated successfully, but these errors were encountered: