Alignment of using mounted secrets for all deployment paths within Azure Container Apps.
Advanced and customization details to simplify the Azure Container Apps deployment for different use cases.
The use of mounted secrets, needs to align with internal changes to our support guide for deploying on Azure Container Apps. This PR will need to be merged at the same time as the internal changes. Certain aspects of the default azure-container-apps/aca-op-scim-bridge.yaml align to the secret not being passed in base64, thus simplifying deployment.
This change to the mounted secrets involves having a separate .yaml file, azure-container-apps/google-workspace/aca-gw-op-scim-bridge.yaml to apply overtop of the existing deployment to support the Google Workspace secrets.
Pulling the advanced configuration options out of the default README.md into a separate file allows for better external linking to sections, previously held in collapsed sections.
Testing: any commands that reference curl/Invoke-RestMethod to pass the yaml file to use the --yaml at /dev/stdin will need to be updated to reference either the branch path of the updated yaml's or the file directly instead of /dev/stdin
Two main aspects of this PR:
The use of mounted secrets, needs to align with internal changes to our support guide for deploying on Azure Container Apps. This PR will need to be merged at the same time as the internal changes. Certain aspects of the default
azure-container-apps/aca-op-scim-bridge.yaml
align to the secret not being passed in base64, thus simplifying deployment.This change to the mounted secrets involves having a separate .yaml file,
azure-container-apps/google-workspace/aca-gw-op-scim-bridge.yaml
to apply overtop of the existing deployment to support the Google Workspace secrets.Pulling the advanced configuration options out of the default README.md into a separate file allows for better external linking to sections, previously held in collapsed sections.
Testing: any commands that reference curl/Invoke-RestMethod to pass the yaml file to use the --yaml at /dev/stdin will need to be updated to reference either the branch path of the updated yaml's or the file directly instead of /dev/stdin