Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(fdr): [PAGOPA-2611] Add opex #2765

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

chore(fdr): [PAGOPA-2611] Add opex #2765

wants to merge 4 commits into from

Conversation

cap-ang
Copy link
Contributor

@cap-ang cap-ang commented Feb 4, 2025

sh terraform.sh apply weu-uat \
--target=azurerm_portal_dashboard.fdr-soap-dashboard \
--target="azurerm_api_management_api_version_set.api_fdr_api_internal" \
--target="azurerm_api_management_api_version_set.api_fdr_api_org" \
--target="azurerm_api_management_api_version_set.api_fdr_api_psp" \
--target="azurerm_api_management_api_version_set.api_fdr_json_to_xml_api" \
--target="azurerm_api_management_api_version_set.api_fdr_xml_to_json_api"
sh terraform.sh apply weu-uat --target=module.elastic_stack

List of changes

OpEx: SOAP FdR requests dashboard has been added

Motivation and context

Type of changes

  • Add new resources
  • Update configuration to existing resources
  • Remove existing resources

Does this introduce a change to production resources with possible user impact?

  • Yes, users may be impacted applying this change
  • No

Does this introduce an unwanted change on infrastructure? Check terraform plan execution result

  • Yes
  • No

Other information


If PR is partially applied, why? (reserved to mantainers)

@cap-ang cap-ang added env: uat The status refers to UAT environment status: applied ✋ labels Feb 4, 2025
@cap-ang cap-ang self-assigned this Feb 4, 2025
@cap-ang cap-ang requested review from a team as code owners February 4, 2025 13:52
@cap-ang cap-ang changed the title Pagopa 2611 chore: PAGOPA-2611 Add opex Feb 4, 2025
@cap-ang cap-ang changed the title chore: PAGOPA-2611 Add opex chore(FdR-1): PAGOPA-2611 Add opex Feb 4, 2025
@cap-ang cap-ang changed the title chore(FdR-1): PAGOPA-2611 Add opex chore(fdr): PAGOPA-2611 Add opex Feb 4, 2025
@cap-ang cap-ang changed the title chore(fdr): PAGOPA-2611 Add opex chore(fdr): [PAGOPA-2611 Add opex Feb 4, 2025
@cap-ang cap-ang changed the title chore(fdr): [PAGOPA-2611 Add opex chore(fdr): [PAGOPA-2611] Add opex Feb 4, 2025
@cap-ang cap-ang added the fdr The changes refer to FdR domain label Feb 4, 2025
@pasqualespica
Copy link
Contributor

@mamari90 in relation to transition to elk managed I didn't apply this part of the pr (under folder elk-monitoring).
Because I would like to make a point with you and @pagopa/payments-cloud-admin first about new ELK istance.
Are u agree ?
cc @pagopa/pagopa-team-core

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
env: uat The status refers to UAT environment fdr The changes refer to FdR domain status: applied ✋ status: partially applied
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants