Updating Azure SCIM lambda to use secrets manager rather than placeholder values #985
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related ticket:
ministryofjustice/analytical-platform#4271
This PR configures the EntraID SCIM lambda to pull sensitive values from Secrets Manager rather than using placeholders which get overwritten every time terraform runs.
At present, the code is retrieving information from an existing secret. In a follow-on PR, I will import it into terraform management.
Context:
Terraform and function code here:
https://github.com/ministryofjustice/moj-terraform-scim-entra-id
Details on executing the function tests are here:
ministryofjustice/moj-terraform-scim-entra-id#6