You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[WIT-682] MWAA SP does not validate provisioning request
# New features and improvements
- Test coverage for MRs is now exported
- Test coverage artifacts are now saved in the pipeline
- CI optimizations
# Bug fixes
- Implemented proper validation for v1/validate endpoint
- open-generator-cli uses a fixed version
- Enabled akka.loglevel to INFO
# Related issue
Closes WIT-682
# Definition of Done for Feature/Hotfixes
## All Developments
- [x] Feature was implemented as per the requirements
- [x] If some code parts are complex they must be commented with code documentation
- [x] CI/CD is successful
- [x] Code coverage is not reduced, any new code is covered
- [x] E2E/integration tests are successful (whether run locally or in CI/CD)
- [x] If dependencies were changed, be sure that they will not impact the project, that their license is compatible, and that they introduce no vulnerabilities
- [x] Documentation have been updated
* Documentation has been updated with explanation of the new feature if it is user-facing (eg component now has additional setting) or it impacts him in some other way (eg optional field that becomes mandatory)
* If it is a breaking change, we have documented it as such in the MR description in a "Breaking Changes" section
- [x] Check that you are not affecting any existing environments with these changes, especially the Sandbox/Playground. This means that merging it to master and deploying it to these environments will not break them and **no manual operations that are not reported in the documentation will be needed**
- [x] Check that nothing is out of order and nothing problematic is included in the changes (sensitive information, credentials, customer information or other intellectual property) as they could end up being public (we have Open Source SP already published and automatically mirrored)
- [x] Security, Authentication and Authorization have been considered. No SQL injection, tokens handling, RBAC integration. Common security vulnerabilities identified and resolved
## API Development
- [x] Semantic of API has been checked, it is comprehensible, meaningful, with no redundant information and user oriented
- [x] Meaningful unit and integration tests are present
- [x] API Parameters are checked and errors are handled
- [x] Returned errors are meaningful to the user
- [x] API contract has been defined and documented. Documentation means explaining the meaning of all fields and including at least one example
- [x] Exceptions and errors are handled, without letting the underlying framework to respond with a generic Internal Server Error
- [x] API Performance has been assessed and is good for real world use cases. Database accesses have been optimized.
- [x] API is logging in compliance with audit standards, presence of sensitive information for GDPR has been assessed and removed or managed in case is needed
## DB Development
- [x] The database schema is designed to accurately represent the data model and meet the requirements
- [x] Tables, relationships, and constraints (e.g. primary keys, foreign keys, unique constraints) are defined appropriately and following a common convention
- [x] Normalization principles are applied to eliminate data redundancy and ensure data integrity
- [x] Schema semantic is meaningful
- [x] Fields naming are following naming convention ( Ex. camelCase or snake_case)
- [x] No fields with mixed behaviors and meaning. If a field is representing an enum, enum values are strongly mutually exclusive
- [x] Data Types have been reviewed and they are a good fit for each field
- [x] Indexes are defined to optimize query performance for frequently accessed data, paying attention to do not affect too much write path and the overall complexity
- [x] Sensitive data is stored securely, encrypted if required, and access is restricted to authorized users
- [x] Backup and restore procedures have been updated to introduce new or changed tables
- [x] Migration scripts to upgrade and downgrade the database have been implemented and tested
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@
6
6
7
7
Designed by [Agile Lab](https://www.agilelab.it/), witboost is a versatile platform that addresses a wide range of sophisticated data engineering challenges. It enables businesses to discover, enhance, and productize their data, fostering the creation of automated data platforms that adhere to the highest standards of data governance. Want to know more about witboost? Check it out [here](https://www.agilelab.it/witboost) or [contact us!](https://www.agilelab.it/contacts).
8
8
9
-
This repository is part of our Open Source projects meant to showcase witboost's integration capabilities and provide a "batteries-included" product.
9
+
This repository is part of our [Starter Kit](https://github.com/agile-lab-dev/witboost-starter-kit) meant to showcase witboost's integration capabilities and provide a "batteries-included" product.
Copy file name to clipboardExpand all lines: aws-integration/src/main/scala/it/agilelab/datamesh/mwaaspecificprovisioner/s3/gateway/S3GatewayError.scala
Copy file name to clipboardExpand all lines: src/main/scala/it/agilelab/datamesh/mwaaspecificprovisioner/api/intepreter/ProvisionerApiMarshallerImpl.scala
+3Lines changed: 3 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -133,6 +133,9 @@ class ProvisionerApiMarshallerImpl extends SpecificProvisionerApiMarshaller {
Copy file name to clipboardExpand all lines: src/main/scala/it/agilelab/datamesh/mwaaspecificprovisioner/api/intepreter/ProvisionerApiServiceImpl.scala
s"An unexpected error occurred while processing the request. Please try again and if the problem persists contact the platform team. Details: ${t.getMessage}"
70
+
))
71
+
}
79
72
80
73
/** Code: 200, Message: It synchronously returns the request result, DataType: String
s"An unexpected error occurred while processing the request. Please try again and if the problem persists contact the platform team. Details: ${t.getMessage}"
93
+
))
94
+
}
89
95
90
96
/** Code: 200, Message: It synchronously returns the request result, DataType: ProvisioningStatus
91
97
* Code: 202, Message: If successful returns a provisioning deployment task token that can be used for polling the request status, DataType: String
@@ -98,22 +104,16 @@ class ProvisionerApiServiceImpl(mwaaManager: MwaaManager) extends SpecificProvis
s"An unexpected error occurred while processing the request. Please try again and if the problem persists contact the platform team. Details: ${t.getMessage}"
116
+
))
117
117
}
118
118
119
119
/** Code: 200, Message: It synchronously returns the access request response, DataType: ProvisioningStatus
@@ -126,7 +126,7 @@ class ProvisionerApiServiceImpl(mwaaManager: MwaaManager) extends SpecificProvis
0 commit comments