feat: [UPBE-590] swagger creation - report generation

src/idpay/20_apim_api_data_factory.tf

@@ -0,0 +1,50 @@
+# #
+# # IDPAY API for internal use from data factory
+# #
+#
+
+resource "azurerm_api_management_api" "idpay_data_factory" {
+  name                = "${var.env_short}-idpay-itn-data-factory"
+  api_management_name = data.azurerm_api_management.apim_core.name
+  resource_group_name = data.azurerm_resource_group.apim_rg.name
+
+  revision              = "1"
+  display_name          = "IDPAY ITN Data Factory"
+  path                  = "idpay-itn/df"
+  subscription_required = false
+  #service_url           = ""
+  protocols = ["https"]
+
+}
+
+resource "azurerm_api_management_api_operation" "idpay_df_report_patch" {
+  operation_id        = "idpay-df-report-patch"
+  api_name            = azurerm_api_management_api.idpay_data_factory.name
+  api_management_name = data.azurerm_api_management.apim_core.name
+  resource_group_name = data.azurerm_resource_group.apim_rg.name
+  display_name        = "IDPAY DF Report Patch"
+  method              = "PATCH"
+  url_template        = "/initiatives/{initiativeId}/reports/{reportId}"
+  template_parameter {
+    name     = "initiativeId"
+    type     = "string"
+    required = true
+  }
+  template_parameter {
+    name     = "reportId"
+    type     = "string"
+    required = true
+  }
+  description = "Endpoint for DF in order to perform a report patch for update the status"
+}
+
+resource "azurerm_api_management_api_operation_policy" "idpay_df_report_patch_policy" {
+  api_name            = azurerm_api_management_api_operation.idpay_df_report_patch.api_name
+  api_management_name = azurerm_api_management_api_operation.idpay_df_report_patch.api_management_name
+  resource_group_name = azurerm_api_management_api_operation.idpay_df_report_patch.resource_group_name
+  operation_id        = azurerm_api_management_api_operation.idpay_df_report_patch.operation_id
+
+  xml_content = templatefile("./apim/api/idpay_data_factory/patch-report-policy.xml.tpl", {
+    ingress_load_balancer_hostname = local.domain_aks_ingress_hostname
+  })
+}

src/idpay/20_apim_api_portal.tf

@@ -569,6 +569,27 @@ module "idpay_itn_merchant_portal" {
         ingress_load_balancer_hostname = local.domain_aks_ingress_hostname
       })
     },
+    {
+      operation_id = "generateReport"
+
+      xml_content = templatefile("./apim/api/idpay_merchant/post-generate-report-policy.xml.tpl", {
+        ingress_load_balancer_hostname = local.domain_aks_ingress_hostname
+      })
+    },
+    {
+      operation_id = "getMerchantTransactionsReports"
+
+      xml_content = templatefile("./apim/api/idpay_merchant/get-report-list-policy.xml.tpl", {
+        ingress_load_balancer_hostname = local.domain_aks_ingress_hostname
+      })
+    },
+    {
+      operation_id = "downloadTransactionsReport"
+
+      xml_content = templatefile("./apim/api/idpay_merchant/get-report-download-policy.xml.tpl", {
+       ingress_load_balancer_hostname = local.domain_aks_ingress_hostname
+      })
+    },
     {
       operation_id = "getRewardBatches"
 

src/idpay/apim/api/idpay_data_factory/patch-report-policy.xml.tpl

@@ -0,0 +1,28 @@
+<!--
+    IMPORTANT:
+    - Policy elements can appear only within the <inbound>, <outbound>, <backend> section elements.
+    - To apply a policy to the incoming request (before it is forwarded to the backend service), place a corresponding policy element within the <inbound> section element.
+    - To apply a policy to the outgoing response (before it is sent back to the caller), place a corresponding policy element within the <outbound> section element.
+    - To add a policy, place the cursor at the desired insertion point and select a policy from the sidebar.
+    - To remove a policy, delete the corresponding policy statement from the policy document.
+    - Position the <base> element within a section element to inherit all policies from the corresponding section element in the enclosing scope.
+    - Remove the <base> element to prevent inheriting policies from the corresponding section element in the enclosing scope.
+    - Policies are applied in the order of their appearance, from the top down.
+    - Comments within policy elements are not supported and may disappear. Place your comments between policy elements or at a higher level scope.
+-->
+<policies>
+    <inbound>
+        <base />
+        <set-backend-service base-url="https://${ingress_load_balancer_hostname}/idpaytransactions" />
+        <rewrite-uri template="@("/idpay/merchant/portal/initiatives/{initiativeId}/reports/{reportId}")"/>
+    </inbound>
+    <backend>
+        <base />
+    </backend>
+    <outbound>
+        <base />
+    </outbound>
+    <on-error>
+        <base />
+    </on-error>
+</policies>

src/idpay/apim/api/idpay_merchant/get-report-download-policy.xml.tpl

@@ -0,0 +1,29 @@
+<!--
+    IMPORTANT:
+    - Policy elements can appear only within the <inbound>, <outbound>, <backend> section elements.
+    - To apply a policy to the incoming request (before it is forwarded to the backend service), place a corresponding policy element within the <inbound> section element.
+    - To apply a policy to the outgoing response (before it is sent back to the caller), place a corresponding policy element within the <outbound> section element.
+    - To add a policy, place the cursor at the desired insertion point and select a policy from the sidebar.
+    - To remove a policy, delete the corresponding policy statement from the policy document.
+    - Position the <base> element within a section element to inherit all policies from the corresponding section element in the enclosing scope.
+    - Remove the <base> element to prevent inheriting policies from the corresponding section element in the enclosing scope.
+    - Policies are applied in the order of their appearance, from the top down.
+    - Comments within policy elements are not supported and may disappear. Place your comments between policy elements or at a higher level scope.
+-->
+<policies>
+    <inbound>
+        <base />
+
+        <set-backend-service base-url="https://${ingress_load_balancer_hostname}/idpaytransactions" />
+        <rewrite-uri template="@("/idpay/merchant/portal/initiatives/{initiativeId}/reports/{reportId}/download")" />
+    </inbound>
+    <backend>
+        <base />
+    </backend>
+    <outbound>
+        <base />
+    </outbound>
+    <on-error>
+        <base />
+    </on-error>
+</policies>

src/idpay/apim/api/idpay_merchant/get-report-list-policy.xml.tpl

@@ -0,0 +1,29 @@
+<!--
+    IMPORTANT:
+    - Policy elements can appear only within the <inbound>, <outbound>, <backend> section elements.
+    - To apply a policy to the incoming request (before it is forwarded to the backend service), place a corresponding policy element within the <inbound> section element.
+    - To apply a policy to the outgoing response (before it is sent back to the caller), place a corresponding policy element within the <outbound> section element.
+    - To add a policy, place the cursor at the desired insertion point and select a policy from the sidebar.
+    - To remove a policy, delete the corresponding policy statement from the policy document.
+    - Position the <base> element within a section element to inherit all policies from the corresponding section element in the enclosing scope.
+    - Remove the <base> element to prevent inheriting policies from the corresponding section element in the enclosing scope.
+    - Policies are applied in the order of their appearance, from the top down.
+    - Comments within policy elements are not supported and may disappear. Place your comments between policy elements or at a higher level scope.
+-->
+<policies>
+    <inbound>
+        <base />
+
+        <set-backend-service base-url="https://${ingress_load_balancer_hostname}/idpaytransactions" />
+        <rewrite-uri template="@("/idpay/merchant/portal/initiatives/{initiativeId}/reports")" />
+    </inbound>
+    <backend>
+        <base />
+    </backend>
+    <outbound>
+        <base />
+    </outbound>
+    <on-error>
+        <base />
+    </on-error>
+</policies>