{"action":"created","issue":{"url":"https://api.github.com/repos/syndesisio/syndesis-project/issues/151","repository_url":"https://api.github.com/repos/syndesisio/syndesis-project","labels_url":"https://api.github.com/repos/syndesisio/syndesis-project/issues/151/labels{/name}","comments_url":"https://api.github.com/repos/syndesisio/syndesis-project/issues/151/comments","events_url":"https://api.github.com/repos/syndesisio/syndesis-project/issues/151/events","html_url":"https://github.com/syndesisio/syndesis-project/issues/151","id":268414065,"number":151,"title":"As a developer, develop custom steps for Syndesis","user":{"login":"kcbabo","id":340837,"avatar_url":"https://avatars1.githubusercontent.com/u/340837?v=4","gravatar_id":"","url":"https://api.github.com/users/kcbabo","html_url":"https://github.com/kcbabo","followers_url":"https://api.github.com/users/kcbabo/followers","following_url":"https://api.github.com/users/kcbabo/following{/other_user}","gists_url":"https://api.github.com/users/kcbabo/gists{/gist_id}","starred_url":"https://api.github.com/users/kcbabo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kcbabo/subscriptions","organizations_url":"https://api.github.com/users/kcbabo/orgs","repos_url":"https://api.github.com/users/kcbabo/repos","events_url":"https://api.github.com/users/kcbabo/events{/privacy}","received_events_url":"https://api.github.com/users/kcbabo/received_events","type":"User","site_admin":false},"labels":[{"id":617567984,"url":"https://api.github.com/repos/syndesisio/syndesis-project/labels/Epic","name":"Epic","color":"3E4B9E","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2017-10-25T14:13:25Z","updated_at":"2017-10-26T15:03:13Z","closed_at":null,"author_association":"NONE","body":"As a developer, I need to help citizen integrators on my team when they need functionality in an integration flow that is not provided OOTB by Syndesis.  This functionality often involves code and/or technical configuration outside the expertise of our citizen integrators.  To address this need, I want to use my traditional Camel development environment to create Camel routes and package those as steps that can be invoked from an integration flow by citizen integrators.  My team refers to these extension packages as \"technical extensions\".\r\n\r\nIt should be possible to create technical extensions using any development environment. An archetype or sample project should be provided which defaults to the correct packaging configuration along with sample metadata and configuration.  RH DevStudio should contain a specific project wizard for creating technical extensions.\r\n\r\nEach technical extension can contain one or more Camel routes which can be used as steps within an integration flow.  Routes can use the Java or XML DSL.  Developers should be able to declare and leverage additional beans and have full access to the CamelContext for their extension.  All technical extension projects should be self-contained and runnable outside of the Syndesis environment to facilitate independent unit testing of the extension.\r\n\r\nSteps contributed by a technical extension should appear as native steps within the Syndesis environment.  Developers must define required metadata for each step contained within a technical extension, including : step name, step description, input data type and output data type.  If an extension does not require data type information and/or does not change the data's type, then the data type metadata is optional.  Additionally, the developer can provide a name and description of the tech extension itself in its metadata."},"comment":{"url":"https://api.github.com/repos/syndesisio/syndesis-project/issues/comments/339695646","html_url":"https://github.com/syndesisio/syndesis-project/issues/151#issuecomment-339695646","issue_url":"https://api.github.com/repos/syndesisio/syndesis-project/issues/151","id":339695646,"user":{"login":"apupier","id":1105127,"avatar_url":"https://avatars2.githubusercontent.com/u/1105127?v=4","gravatar_id":"","url":"https://api.github.com/users/apupier","html_url":"https://github.com/apupier","followers_url":"https://api.github.com/users/apupier/followers","following_url":"https://api.github.com/users/apupier/following{/other_user}","gists_url":"https://api.github.com/users/apupier/gists{/gist_id}","starred_url":"https://api.github.com/users/apupier/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/apupier/subscriptions","organizations_url":"https://api.github.com/users/apupier/orgs","repos_url":"https://api.github.com/users/apupier/repos","events_url":"https://api.github.com/users/apupier/events{/privacy}","received_events_url":"https://api.github.com/users/apupier/received_events","type":"User","site_admin":false},"created_at":"2017-10-26T15:03:13Z","updated_at":"2017-10-26T15:03:13Z","author_association":"NONE","body":"> ok so for this first iteration only web based upload is supported, should we open an issue to investigate RH DevStudio authentication ?\r\n\r\nLars created this \"Feature request\" for the deployment part: https://issues.jboss.org/browse/FUSETOOLS-2630\r\nI think we can reuse it to specify what we need on Fuse Tooling side."}}
{"actor":{"display_login":"apupier"}}