- Recipes
- Github repository files to Elasticsearch
Connect Github repository files and Elasticsearch in our serverless environment
Use this template to Get files from Github repository using them to insert rows into Elasticsearch table.
Share
Get files from Github repository
Used integrations:
JavaScript
Python
class GithubSourceRepositoryFiles {
async init() {
// TODO: Create your github credential
// More info at https://yepcode.io/docs/integrations/github/#credential-configuration
this.github = yepcode.integration.github("your-github-credential-name");
// TODO: Customize the repo name and owner
this.repositoryOwner = "your-github-username";
this.repositoryName = "your-repository-name";
}
async fetch(publish, done) {
// TODO: Customize the path you want to obtain all files in it and its subdirectories (if has)
// It can also be a file path to only obtain one file
// If you pass undefined you will obtain the entire repository content
await this._publishPathContent("/path-in-repo", publish);
done();
}
_isFileContent = isString;
_isDirectoryInfo = isObject;
_publishPathContent = async (path, publishCallback) => {
// More info of this request at: https://docs.github.com/en/rest/repos/contents#get-repository-content
const response = await this.github.rest.repos.getContent({
mediaType: {
format: "raw",
},
owner: this.repositoryOwner,
repo: this.repositoryName,
path: path,
});
const {
data
} = response;
if (this._isFileContent(data)) {
// TODO: Customize the item to publish for each file in the repository
publishCallback({
path,
content: data
});
return;
}
if (this._isDirectoryInfo(data)) {
for (const directoryEntry of data) {
await this._publishPathContent(directoryEntry.path, publishCallback);
}
return;
}
console.error("Unexpected data type: ", response.headers["content-type"]);
};
async close() {}
}
Comming soon
We are releasing new Python recipes every week
Do you need help solving this integration with YepCode?
Let's talkInsert rows into Elasticsearch table
Used integrations:
JavaScript
Python
class ElasticsearchTargetInsert {
async init() {
// TODO: Create your clickhouse credential
// More info at https://yepcode.io/docs/integrations/elasticsearch/#credential-configuration
this.elasticsearch = yepcode.integration.elasticsearch(
"your-elasticsearch-credential-name"
);
}
async consume(item) {
// TODO: Map your item to row
await this.elasticsearch.index({
index: "your_table_name",
document: item,
});
}
async close() {}
}
class ElasticsearchTargetInsert:
def setup(self):
# TODO: Create your elasticsearch credential
# More info at https://yepcode.io/docs/integrations/elasticsearch/#credential-configuration
self.elasticsearch = yepcode.integration.elasticsearch("your-elasticsearch-credential-name")
def consume(self, generator, done):
for item in generator:
self.process(item)
done()
def process(self, item):
# TODO: Customize your index name
self.elasticsearch.index(index="index-name", document=item)
def close(self):
pass
FAQs
YepCode is a SaaS platform that allows to create, execute and monitor integrations and automations using source code in a serverless environment.
We like to call it the Zapier for developers, since we bring all the agility and benefits of NoCode tools (avoid server provisioning, environment configuration, deployments,...), but with all the power of being able to use a programming language like JavaScript or Python.
These recipes are a good starting point for you to build your own YepCode processes and solve your integration and automation problems.
You only have to fill the sign up form and your account will be created with our FREE plan (no credit card required).
YepCode has been created with a clear enterprise approach (multi-tenant environment, team management, high security and auditing standards, IdP integrations, on-premise options,...) so we can be the Swiss army knife of any team of engineering, especially those that need to extract or send information to external systems, and where a certain dynamism or adaptation to change is necessary in that process.
Sure! You just need to do some configuration to allow YepCode servers to connect to that service. Check our docs page to get more information.
Ask us for help to solve your integration problem
Recipes may be used in a self service approach cloning them to one YepCode account, but if you are looking for a turnkey approach, our team may help you.