Noah Paige

## Design Considerations ### Repository Location For the data.all SDK/CLI, we will host the SDK and CLI packages within a new repository (separate from data.all OS but within the same...

> Certainly , great feature to have. Q. As there are plans to use AppSync for GQL , will the also seemlessly work with AppSync ? Yes! It will work...

Thanks both for the great comments + questions above, here are some thoughts/response Response to @zsaltys Comments: - (1)For building the schema file - the simplest case and the initial...

Leaving in draft state until additional permission restrictions added to lambda roles and dbmigration role

Hi @mourya-33 - left one minor comment and can you run `ruff format` and commit the changes ( I see the ruff workflow is failing) I will do a quick...

Tested: - [x] CICD Pipeline Completes - [x] CodePipeline CB Policy Updated - [x] Cross Account Cloudfront Role Updated - [x] DB Migration Role Updated - [x] Lambda Roles Updated...

Thanks for raising this issue @zsaltys. Data.all supports 2 ways of creating the pivotRole, via CloudFormation before linking Environment, or via CDK when linking Environment. Some of the pain points...

This feature to allow Admins to re-index the data.all Catalog has been implemented in PR #1365 It allows Admins to run re-index catalog tasks to sync catalog objects with data.all...

Thanks for raising this issue @zsaltys, we will have to investigate which roles Checkov is reporting as non-compliant and ensure we can restrict them further, but yes theoretically every write...

From discussion with @TejasRGitHub: 1. During maintenance window - only block mutations instead of blocking all calls to graphQL (for non DA Admins) - No need for a new custom...