Now allows tenant config to be pulled with both tenant name or tenant Id. The original path /tenant-config/{tenantName} is unchanged, but added support for the query parameter tenantId. Ex: /tenant-config?tenantId=abc123
Reason for this change
The EKS SaaS Reference architecture doesn't have access to the tenant-name, so it needed to be able to resolve tenant auth information based on tenant id.
Now allows tenant config to be pulled with both tenant name or tenant Id. The original path
/tenant-config/{tenantName}is unchanged, but added support for the query parametertenantId. Ex:/tenant-config?tenantId=abc123Reason for this change
The EKS SaaS Reference architecture doesn't have access to the tenant-name, so it needed to be able to resolve tenant auth information based on tenant id.
Description of changes
The tenant-config python lambda file
Checklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.