-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: [P4PU-000] Promote to MAIN #162
Merged
Merged
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
* added redis cache * added redis cache * updated log level * updated redis config and added caching for oauth2 state * updated redis config and added caching for oauth2 state * updated test * updated test * updated test and implementation * updated test * updated test * updated test * Update src/main/java/it/gov/pagopa/arc/security/OAuth2StateStoreRepository.java Co-authored-by: antonioT90 <[email protected]> * Update src/test/java/it/gov/pagopa/arc/security/IdpIntegrationTest.java Co-authored-by: antonioT90 <[email protected]> * updated test * Update src/test/java/it/gov/pagopa/arc/service/TokenStoreServiceImplTest.java Co-authored-by: antonioT90 <[email protected]> * updated test * updated test * Update src/test/java/it/gov/pagopa/arc/security/RedisOAuth2AuthorizationRequestRepositoryTest.java Co-authored-by: antonioT90 <[email protected]> * updated test * Update src/main/java/it/gov/pagopa/arc/config/RedisConfig.java Co-authored-by: antonioT90 <[email protected]> * updated test * updated test name --------- Co-authored-by: antonioT90 <[email protected]>
feat: [P4PU-549] added redis cache (#134) * added redis cache * added redis cache * updated log level * updated redis config and added caching for oauth2 state * updated redis config and added caching for oauth2 state * updated test * updated test * updated test and implementation * updated test * updated test * updated test * Update src/main/java/it/gov/pagopa/arc/security/OAuth2StateStoreRepository.java * Update src/test/java/it/gov/pagopa/arc/security/IdpIntegrationTest.java * updated test * Update src/test/java/it/gov/pagopa/arc/service/TokenStoreServiceImplTest.java * updated test * updated test * Update src/test/java/it/gov/pagopa/arc/security/RedisOAuth2AuthorizationRequestRepositoryTest.java * updated test * Update src/main/java/it/gov/pagopa/arc/config/RedisConfig.java * updated test * updated test name --------- Co-authored-by: antonioT90 <[email protected]>
* P4PU-590 updated swagger * P4PU-590 updated MapperUtilities * P4PU-590 updated Mapper with convertToZonedDateTimeAndTruncateSeconds * P4PU-590 updated tests
<!--- Please always add a PR description as if nobody knows anything about the context these changes come from. --> <!--- Even if we are all from our internal team, we may not be on the same page. --> <!--- Write this PR as you were contributing to a public OSS project, where nobody knows you and you have to earn their trust. --> <!--- This will improve our projects in the long run! Thanks. --> #### List of Changes - Added redis cache - updated date type returned by payment-notices <!--- Describe your changes in detail --> #### Motivation and Context <!--- Why is this change required? What problem does it solve? --> #### How Has This Been Tested? <!--- Please describe in detail how you tested your changes. --> <!--- Include details of your testing environment, tests ran to see how --> <!--- your change affects other areas of the code, etc. --> #### Screenshots (if appropriate): #### Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) #### Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] My change requires a change to the documentation. - [ ] I have updated the documentation accordingly.
* removed transcation detail * removed transcation detail * removed transcation detail postman * removed transcation detail postman * removed transcation detail
* removed transcation receipt * removed transcation receipt * RESTORED BizEventsReceiptNotFoundException
…ion (#146) removed api call to removed api from postman collection
removing lombok config
fix code review trigger condition
* P4PU-538 removed connector and updated application.yml * P4PU-538 removed dto * P4PU-538 updated swagger and service * P4PU-538 removed stub * P4PU-538 updated tests * P4PU-538 updated collection postman and template
<!--- Please always add a PR description as if nobody knows anything about the context these changes come from. --> <!--- Even if we are all from our internal team, we may not be on the same page. --> <!--- Write this PR as you were contributing to a public OSS project, where nobody knows you and you have to earn their trust. --> <!--- This will improve our projects in the long run! Thanks. --> #### List of Changes - Removed transactions list api - Removed transactions details api - Removed transactions receipt api <!--- Describe your changes in detail --> #### Motivation and Context <!--- Why is this change required? What problem does it solve? --> #### How Has This Been Tested? <!--- Please describe in detail how you tested your changes. --> <!--- Include details of your testing environment, tests ran to see how --> <!--- your change affects other areas of the code, etc. --> #### Screenshots (if appropriate): #### Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) #### Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] My change requires a change to the documentation. - [ ] I have updated the documentation accordingly.
* P4PU-327 updated code-review with libraries and exclusions * P4PU-327 updated code-review and sonarqube version
* P4PU-678 updated exclusions * P4PU-678 removed quotes * P4PU-678 updated exclusions
P4PU-682 updated exclusions
* updated snapshot trigger for argocd * added postman env * pre-commit configuration fixed * pre-commit fixs * pre-commit version updated * removed fake env for postman
fix exclusions pattern code-review
P4PU-685 logging traceId and userId
* P4PU-687 added log level debug to connector * P4PU-687 added custom feign client logger * P4PU-687 updated CustomFeignClientLogger and feignClient * P4PU-687 added test * P4PU-687 updated payment notices * P4PU-687 updated tests * P4PU-687 updated CustomFeignClientLogger * P4PU-687 added test * P4PU-687 updated var prefix
<!--- Please always add a PR description as if nobody knows anything about the context these changes come from. --> <!--- Even if we are all from our internal team, we may not be on the same page. --> <!--- Write this PR as you were contributing to a public OSS project, where nobody knows you and you have to earn their trust. --> <!--- This will improve our projects in the long run! Thanks. --> #### List of Changes - added Logger traceId and userId - added Custom Feign Client Logger - fixed code review exclusion patterns <!--- Describe your changes in detail --> #### Motivation and Context <!--- Why is this change required? What problem does it solve? --> #### How Has This Been Tested? <!--- Please describe in detail how you tested your changes. --> <!--- Include details of your testing environment, tests ran to see how --> <!--- your change affects other areas of the code, etc. --> #### Screenshots (if appropriate): #### Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) #### Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] My change requires a change to the documentation. - [ ] I have updated the documentation accordingly.
Quality Gate passedIssues Measures |
Giuseppe-LaManna
requested review from
oleksiybozhykntt,
antonioT90 and
a team
as code owners
November 20, 2024 11:58
antonioT90
approved these changes
Nov 20, 2024
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.
List of Changes
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: