Added capability to use custom secret names for Lambda - Githubissues

awslabs / ssosync

Populate AWS SSO directly with your G Suite users and groups using either a CLI or AWS Lambda

Apache License 2.0

512 stars 175 forks source link

Added capability to use custom secret names for Lambda #173

Closed anggras closed 5 months ago

anggras commented 6 months ago

Issue #, if available: https://github.com/awslabs/ssosync/issues/170

Description of changes:

Environment Variables

Added support for the following env variables:

SSOSYNC_GOOGLE_CREDENTIALS_SECRET_ID -> fallback to SSOSYNC_GOOGLE_CREDENTIALS
SSOSYNC_GOOGLE_ADMIN_SECRET_ID -> fallback to SSOSYNC_GOOGLE_ADMIN
SSOSYNC_SCIM_ENDPOINT_SECRET_ID -> fallback to SSOSYNC_SCIM_ENDPOINT
SSOSYNC_SCIM_ACCESS_TOKEN_SECRET_ID -> fallback to SSOSYNC_SCIM_ACCESS_TOKEN
SSOSYNC_REGION_SECRET_ID -> fallback to SSOSYNC_REGION
SSOSYNC_IDENTITY_STORE_ID_SECRET_ID -> fallback to SSOSYNC_IDENTITY_STORE_ID

Viper

Updated to Viper 1.18.2

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.