feat: [PAGOPA-2625] Defining FdR-Fase3 PostgreSQL infra and all related pipelines #2768
+543
−4
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.
This PR contains the definition of a new resource for FdR project. In detail, the changes are related to the definition of a new PostgreSQL database for FdR-Fase3 context. The new database is included in the same PostgreSQL Flexible Server of the FdR-Fase1 DB, in order to use the same context and reduce the proliferation of different servers.
In order to define the schema, tables, indexes and more, the PR also contains the definition of the needed resources via Liquibase XML file, adding new Azure DevOps pipelines for automatize processes and applies.
List of changes
Motivation and context
These changes are required in order to migrate FdR-Fase3 persistence on PostgreSQL database.
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)