Noah Paige

Yes I believe implemented in https://github.com/data-dot-all/dataall/pull/1094 and addressed also in https://github.com/data-dot-all/dataall/issues/1092 I will close both issues as complete - thanks @zsaltys

closing as completed in #1094

We have feature flags to enable / disable file upload altogether for a data.all deployment but if file upload actions are enabled we currently do not conditionally disable the upload...

Hi @anandsumit2000, I believe you will run into some issues if you are trying to create multiple of the same VPC endpoints within the same AWS account region pair. Data.all...

I see the issue now... I think the easiest resolution to avoid any duplication of resources and/or any potential errors would be to extend to logic we have for Deployment...

Hi @zsaltys - I think the above idea is one that we would want to pick up for a future release of data.all as it would be very helpful for...

Re-opening this issue - think was accidently auto closed with the merge of #1422

Just 1 pending comment on migration script Otherwise I think this PR is good and it solves issue #1171 but I am not sure it solves #1173 completely. For that...

if i understand correctly - this issue describes the case where GroupA is a member of EnvA and EnvB and has access to TableX via share requestos from both GroupA...

TLDR - I think the easiest approach would be to update the way we manage deletes to resolve this issue... If we want to more cautious and "future proof" maybe...