terraform-snowflake-api-integration-with-geff-aws icon indicating copy to clipboard operation
terraform-snowflake-api-integration-with-geff-aws copied to clipboard

Terraform module to create resources across the Snowflake and AWS providers and establish proper relationships within those resources.

Results 14 terraform-snowflake-api-integration-with-geff-aws issues
Sort by recently updated
recently updated
newest added

``` │ with module.pat_geff_shs.module.storage_integration.snowflake_integration_grant.this, │ on .terraform/modules/pat_geff_shs.storage_integration/storage_integration.tf line 22, in resource "snowflake_integration_grant" "this": │ 22: resource "snowflake_integration_grant" "this" { │ │ This resource is deprecated and will be removed in...

- Lambda metrics - API Gateway metrics

use `geff-` to provision IAM policy to provide access to secrets manager secrets.

We should take additional data buckets in order for `s3_reader` role to have IAM only S3 bucket for storage only pipelines.

Rather than building the archive dynamically each time, it's better to take a s3 path for the zip archive and update the lambda based on that path.

Allow both but with a priority? How does the snowflake terraform provider do it?

Add variables that are used turn on/off specific integration and resources as one may want to use only the storage side of the pipeline or only the api side of...

Allow for variables where you can pass an existing role for each of the 4 roles: 1. gateway caller 2. s3 Reader 3. gateway logger 4. lambda role

In this function: ``` def process_row( data: Optional[Text] = None, base_url: Text = '', url: Text = '', json: Optional[Text] = None, method: Text = 'get', headers: Text = '',...