When developing your own integration components for the elastic.io platform, you need to structure your work into Git repositories. Each repository represents an integration component and gets used to push your local code to elastic.io remote server. Every push results in a new deployment of the component.
The access to the component repository is restricted to a team the repository belongs to. Each member of the team can change, configure and deploy a component. The team itself belongs to an organization and so only members of the organization can be invited to the team.
A developer team controls access to the component repositories belonging to that team. The team members may collaborate on common integration component in integration projects.
Note: you must have organisation
Adminprivileges for this to work.
To create a new developer team navigate to the Developers section and click on a button + Add New Team as it shown on the screenshot below:
After clicking the button a menu is presented to enter the name of your team:
The naming of the team must adhere to specific rules:
Note: use letters, digits,
_to name your team. No spaces!
After creating the team you are automatically becoming the member of that team.
You can proceed to either creating your first repository in this team and push your custom component or you can invite your fellow developers into the same team to collaborate in the development of that particular component.
To invite your colleagues into your development team to work on the same custom component click Invite developer button to be presented with the menu like this:
To invite a developer, click on the check-mark in front of the their names and then click on the Send Invites. The developers will receive invitation to by e-mail and would need to accept it to join the team.
Note, only members of the same organisation can be invited into this developer team. The list shows all the possible members that can be invited to this current team.
You can skip to the integration component repository creation section from here. Otherwise if you need to delete a developer team continue to the next section.
If you need to delete a developer team:
If the above conditions are true, you can proceed and delete the developer team using an API call.
Almost every developer has worked with some sort of version control and repository management. GitHub, one of the most famous code developing and collaborating platforms, is the most famous for its use of repository practice. We use the same tactics which give developers complete autonomy to manage their code.
Note: Remind your fellow developers to follow the same procedure and upload their own unique SSH Key before proceeding further.
As mentioned above, each repository represents a component. That’s why we use repository and component terms interchangeably here. Every component resides in a particular repository.
To create a repository click on New Repo button and input the desired name and press Save.
Note: As with the naming of the teams use letters, digits,
_to name your repository. No spaces!
In this particular example, the name of the repository is
ac-petstore and it
belongs to the
academia_team. The screenshot above includes further instructions and
guidelines on how to proceed further. Here are the necessary steps for the clarity:
git clone https://github.com/elasticio/petstore-component-nodejs.git ac-petstore cd ac-petstore
git remote add ipaas firstname.lastname@example.org:ac-petstore.git git push ipaas master
Here is how the main Development page would look like after the deployment of your custom component:
To manage your repository click on the name to see the following page with details:
This is the URL that you can push the code for deploying the updates.
Note: the cloning of your repositories is not supported. To update the code push it again to create the next version of it. Please contact our support if you need the copy of your repository.
You can set all environment variables for this particular repository by following the link. Consult our documentation on How to define environment variables for integration components.
This feature gives a possibility to set the component as Private, Public and Global:
Teammeans accessible to the current team members.
Publicmeans accessible for entire tenant.
Globalmeans accessible for all tenants - can be set only by support.
Here is the deployment history of the repository containing: