- Recipes
- Amazon S3 NDJSON file to Keycloak users
Connect Amazon S3 NDJSON file and Keycloak users in our serverless environment
Use this template to Read NDJSON file entries from Amazon S3 bucket using them to create Keycloak users.
Share
Read NDJSON file entries from Amazon S3 bucket
Used integrations:
- JavaScript
- Python
class AwsS3SourceReadRemoteNdjson {
async init() {
// TODO: Create your aws-s3 credential
// More info at https://yepcode.io/docs/integrations/aws-s3/#credential-configuration
this.awsS3 = yepcode.integration.awsS3("your-aws-s3-credential-name");
}
async fetch(publish, done) {
// TODO: Customize the command to be executed
// More info at: https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/clients/client-s3/interfaces/getobjectcommandinput.html
const getObjectCommand = new GetObjectCommand({
Bucket: "your-bucket-name",
Key: "your-file-name",
});
const getObjectResult = await this.awsS3.send(getObjectCommand);
getObjectResult.body
.pipe(ndjson.parse())
.on("data", async (line) => {
await publish(line);
})
.on("end", done);
}
async close() {}
}
import ndjson
import io
class AwsS3SourceReadRemoteNdjson:
def setup(self):
# TODO: Create your S3 credential:
# More info at https://yepcode.io/docs/integrations/aws-s3/#credential-configuration
self.aws_s3_client = yepcode.integration.awsS3("your-s3-credential-name")
def generator(self):
# TODO: Customize your bucket name and object key
# See all supported params in: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/s3/client/get_object.html
response = self.aws_s3_client.get_object(
Bucket="your-bucket-name",
Key="your-file-name",
)
bytes_stream = response["Body"]
ndjson_file_stream = io.TextIOWrapper(bytes_stream, encoding="utf-8")
reader = ndjson.reader(ndjson_file_stream)
for row in reader:
yield row
def close(self):
pass
Do you need help solving this integration with YepCode?
Let's talkCreate Keycloak users
Used integrations:
- JavaScript
- Python
class KeycloakTargetCreateUser {
async init() {
// TODO: Create your keycloak credential
// More info at https://yepcode.io/docs/integrations/keycloak/#credential-configuration
this.keycloakClient = await yepcode.integration.keycloak(
"your-keycloak-credential-name"
);
}
async consume(item) {
await this.createUser(item);
}
async createUser({
firstName,
lastName,
email,
username,
password
}) {
// TODO: Customize your new user payload with your item content
// See all available options at: https://www.keycloak.org/docs-api/11.0/rest-api/index.html#_userrepresentation
const payload = {
firstName,
lastName,
email,
username,
enabled: true,
emailVerified: true,
credentials: [{
type: "password",
value: password,
temporary: false
}],
};
return this.keycloakClient.users.create(payload);
}
async close() {}
}
Comming soon
We are releasing new Python recipes every week
FAQs
YepCode is a SaaS platform that enables the creation, execution and monitoring of 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 an excellent starting point for creating your own YepCode processes and solving complex integration and automation problems.
You only have to complete 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 focus, offering a multi-tenant environment, team management capabilities, high security and auditing standards, Identity Provider (IdP) integrations, and on-premise options. It serves as the Swiss army knife for engineering teams, especially those requiring the extraction or transmission of information to external systems. It excels in scenarios demanding flexibility and adaptability to change within the process.
Sure! You only need to configure YepCode servers to establish a connection with that service. Check our docs page to get more information.