- Add comprehensive CouchDB setup and configuration - Update Docker files for CouchDB compatibility - Create Kubernetes manifests for CouchDB deployment - Add migration scripts and documentation - Update seeding scripts to support both CouchDB and MongoDB - Add docker-compose for local development - Create comprehensive setup and deployment guides 🤖 Generated with [AI Assistant] Co-Authored-By: AI Assistant <noreply@ai-assistant.com>
23 lines
1.1 KiB
JavaScript
23 lines
1.1 KiB
JavaScript
"use strict";
|
|
Object.defineProperty(exports, "__esModule", { value: true });
|
|
exports.loadAWSCredentials = loadAWSCredentials;
|
|
const aws_temporary_credentials_1 = require("../../cmap/auth/aws_temporary_credentials");
|
|
/**
|
|
* @internal
|
|
*/
|
|
async function loadAWSCredentials(kmsProviders, provider) {
|
|
const credentialProvider = new aws_temporary_credentials_1.AWSSDKCredentialProvider(provider);
|
|
// We shouldn't ever receive a response from the AWS SDK that doesn't have a `SecretAccessKey`
|
|
// or `AccessKeyId`. However, TS says these fields are optional. We provide empty strings
|
|
// and let libmongocrypt error if we're unable to fetch the required keys.
|
|
const { SecretAccessKey = '', AccessKeyId = '', Token } = await credentialProvider.getCredentials();
|
|
const aws = {
|
|
secretAccessKey: SecretAccessKey,
|
|
accessKeyId: AccessKeyId
|
|
};
|
|
// the AWS session token is only required for temporary credentials so only attach it to the
|
|
// result if it's present in the response from the aws sdk
|
|
Token != null && (aws.sessionToken = Token);
|
|
return { ...kmsProviders, aws };
|
|
}
|
|
//# sourceMappingURL=aws.js.map
|