Sofia Sazonova
Sofia Sazonova
When group is invited to Env or deleted from it, the callback takes a while and user can't see any progress or any kind of reaction , which can be...
# Enforcement Metadata forms can be obligatory to fill in on different levels. User can select the metadata form and entity types, that should have this form attached. Enforcement affects...
### Feature or Bugfix - Feature ### Detail - New Tab in MF View - NO ACCESS RESTRICTION: if entity has an attached form, it's visible in this tab ###...
### Describe the bug 1. ShareObject is created, and all it's sharable items are created at the moment 2. If we delete table from data.all (but it's still in Glue)...
The target features are: Make MFs editable. But what to do with already attached forms? Solution: enable versioning of Metadata Forms.  1. Attached MF should be connected with...
### Feature or Bugfix - Feature ### Detail For group share and consumption role shares perform - [x] Create Share request - [x] Submit request without Items (not allowed) -...
- [ ] MF Enforcement. [Description](https://github.com/data-dot-all/dataall/issues/1065#:~:text=Who%20can%20enforce,a%20specific%20share.) - [ ] MF attachement: - [x] Organizations - [ ] Organization Teams - [x] Environments - [ ] Environment Teams - [x] Datasets...
### Describe the bug revision = '852cdf6cf1e0' While executing code ``` PermissionService.save_permission( session, name=perm, description=ENVIRONMENT_REDSHIFT_ALL_WITH_DESC[perm], permission_type=PermissionType.RESOURCE.name, ) ``` the DB_migration handler throws an error, while performing 'find permission' select: ```...
**Is your idea related to a problem? Please describe.** Branched from https://github.com/data-dot-all/dataall/pull/1444#discussion_r1704507144 **Describe the solution you'd like** Refactor frontend: - [ ] Define commonly used functions as shared components/files. E.g....
### Why do we need DataAll migrations During the work on [data-dot-all#1280](https://github.com/data-dot-all/dataall/pull/1280) we encountered a problem: we need to revise all share-policies in already existed AWS deployments (remove s3:* permissions...