Description
For a Source, transformation_owners_allowed and destinations_allowed feels redundant I want to unify them into transformations_allowed as a data access grant.
Sample Yaml to understand the changes you have to make:
collaborator: Media #name of the collaborator
sources:
- name: Media_customers
csv_location: ./media_customers.csv
description: table having data for media customer
columns:
- name: email
type: string
masking_type: sha256
selectable: true
aggregates_allowed:
- private_count
- private_count_distinct
join_key: true
transformations_allowed:
- ref: /Research/transformation/customer_overlap_count
noise_parameters:
- noiseType: Laplace
- epsilon: math.Log(2)
- maxPartitionsPerUser: 1
Make necessary changes in the address authorization and the graph population logic to enable this yaml.
Description
For a Source,
transformation_owners_allowedanddestinations_allowedfeels redundant I want to unify them intotransformations_allowedas a data access grant.Sample Yaml to understand the changes you have to make:
Make necessary changes in the address authorization and the graph population logic to enable this yaml.