Skip to main content

Connect AWS Redshift and Keycloak users in our serverless environment

Use this template to Read rows from AWS Redshift table using them to create Keycloak users.

Share

Read rows from AWS Redshift table

Used integrations:
class AwsRedshiftSourceSelect {
async init() {
// TODO: Create your aws-redshift credential
// More info at https://yepcode.io/docs/integrations/aws-redshift/#credential-configuration
this.awsRedshift = yepcode.integration.awsRedshift(
"your-aws-redshift-credential-name"
);

// TODO: Customize the command to be executed
// More info at https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/clients/client-redshift-data/interfaces/executestatementcommandinput.html
const {
Id
} = await this.awsRedshift.send(
new ExecuteStatementCommand({
ClusterIdentifier: "your-cluster-identifier",
Database: "your-database-name",
DbUser: "your-database-user",
Sql: "SELECT * FROM your-table-name;",
})
);
this.statementId = Id;
await this._awaitStatementToFinish();
}

async fetch(publish, done) {
let nextToken;
// if result is returned paginated, iterate to publish entire statement result
do {
const result = await this.awsRedshift.send(
new GetStatementResultCommand({
Id: this.statementId,
NextToken: nextToken,
})
);
nextToken = result.NextToken;
for (const record of result.Records) {
// Each record come as a list of record cells
// More info at https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/clients/client-redshift-data/interfaces/getstatementresultcommandoutput.html

// TODO: Customize record columns mapping to the item that will be published
const item = {
id: record.id,
...record
};

await publish(item);
}
} while (nextToken);
done();
}

async close() {}

_awaitStatementToFinish() {
return new Promise((resolve, reject) => {
const describeStatementCommand = new DescribeStatementCommand({
Id: this.statementId,
});

// Configure interval to check statement status
const intervalId = setInterval(async () => {
const result = await this.awsRedshift.send(describeStatementCommand);
if (result.Status === "FINISHED") {
clearInterval(intervalId);
resolve();
return;
}

if (result.Status === "FAILED" || result.Status === "ABORTED") {
clearInterval(intervalId);
reject();
return;
}
}, 1000);
});
}
}

Do you need help solving this integration with YepCode?

Let's talk

Create Keycloak users

Used integrations:
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() {}
}

Other combinations

View recipes

Related recipes

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.