chore: [PAGOPA-2626] Decoupler: logic for FdR SOAP requests #2766
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aomegax
added
env: dev
andrea-deri
reviewed
Feb 10, 2025
src/domains/fdr-app/api/fdr-fase1/nodoPerPa/v1/fdr_pagopa.xml.tpl
Outdated
Show resolved
Hide resolved
src/domains/fdr-app/api/fdr-fase1/nodoPerPsp/v1/fdr_nodoinvia_flussorendicontazione_flow.xml
Show resolved
Hide resolved
pasqualespica
requested changes
Feb 10, 2025
src/domains/fdr-app/api/fdr-fase1/nodoPerPa/v1/fdr_pagopa.xml.tpl
Outdated
Show resolved
Hide resolved
src/domains/fdr-app/api/fdr-fase1/nodoPerPsp/v1/fdr_nodoinvia_flussorendicontazione_flow.xml
Show resolved
Hide resolved
|
@aomegax @andrea-deri after this PR #2775 the apim policy on FDR API, where will they be? On pagopa-infra ( here ) or on pagopa-fdr pagopa/pagopa-fdr#82 ? |
# Conflicts: # src/domains/fdr-app/04_apim_fdr_fase3.tf # src/domains/fdr-app/README.md
Yes, it regards FdR3 not FdR1 policies. It is right. |
…ussiRendicontazione` primitive (#2781) * [PAGOPA-2647] feat: defining response caching for FdR-Fase1 'flow list' API * [PAGOPA-2647] fix: resolving bugs and refactoring code * [PAGOPA-2647] fix: excluding caching process if response returns a fault code * [PAGOPA-2647] fix: updating tracing text * [PAGOPA-2647] fix: resolving bugs and adding correct handling of BLOB headers * [PAGOPA-2647] fix: adding permission for read/write operations by APIM * [PAGOPA-2647] chore: commenting trace tag, avoiding unnecessary log
aomegax
added
status: apply in progress
env: uat
pasqualespica
force-pushed
the
PAGOPA-2626-decoupler
branch
from
f92609b to
45f1b6b
Compare
pasqualespica
removed
env: dev
…er' into PAGOPA-2626-decoupler
pasqualespica
approved these changes
Feb 13, 2025
| <!-- Execute a GET call on blob-storage using the UUID as "search filter" --> | ||
| <authentication-managed-identity resource="https://storage.azure.com/" output-token-variable-name="msi-access-token" ignore-error="false" /> | ||
| <send-request mode="new" response-variable-name="cached_response_content" timeout="300" ignore-error="true"> | ||
| <set-url>@{ return "https://{{fdr_cachedresponse_saname}}.blob.core.windows.net/" + "{{fdr_cachedresponse_containername}}" + "/" + ((string) context.Variables["fdr_cached_response_uuid"]) + ".txt"; }</set-url> |
There was a problem hiding this comment.
remove .txt with empty or .xml ext
|
🎉 This PR is included in version 1.386.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
nodoChiediFlussoRendicontazioneList of changes
Motivation and context
Type of changes
Does this introduce a change to production resources with possible user impact?
Does this introduce an unwanted change on infrastructure? Check terraform plan execution result
Other information
If PR is partially applied, why? (reserved to mantainers)