From 112585af85dedc2e4143ba3214cc8ad87a57e5e8 Mon Sep 17 00:00:00 2001 From: nithyatsu Date: Mon, 4 Nov 2024 14:14:36 -0800 Subject: [PATCH] wip --- .../2024-08-applications-rp-component-threat-model.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/architecture/2024-08-applications-rp-component-threat-model.md b/architecture/2024-08-applications-rp-component-threat-model.md index 66ecb28e..fab298bc 100644 --- a/architecture/2024-08-applications-rp-component-threat-model.md +++ b/architecture/2024-08-applications-rp-component-threat-model.md @@ -34,7 +34,9 @@ Radius secret stores are implemented using kubernetes as secret provider. Applications RP has a key sub component `Recipe Engine` to execute `recipes`. `Recipes` are Bicep or Terraform code that is used to deploy infrastructure components on Azure and AWS. The Bicep recipes are fetched from OCI compliant registries. Terraform recipes are public modules and fetched from internet too. -In order to execute Terraform recipes, Applications RP installs latest Terraform. It mounts a directory `/terraform` in Applications RP pod for executing terraform recipes in this, using the installed executable. The output resources generated from terraform module are converted to Radius output resources and stored in our datastore. +In order to execute Terraform recipes, Applications RP installs latest Terraform. It also mounts an empty directory `/terraform` into Applications RP pod. It uses this directory for executing terraform recipes using the installed executable. The output resources generated from terraform module are converted to Radius output resources and stored in our datastore. + +In order to deploy bicp recipes, Applications RP sends a request to UCP, which in turn forwards it to Deployment Engine. Applications RP also allows users to create their own recipes and use them to provision their infrastructure.