Hello! Is it possible to declare something like a ...
# announcements
b
Hello! Is it possible to declare something like a global input for the solids in the configuration? For instance many solids take the input
bag_cleaned_schema
which I want to pass in the configuration, and preferably only declare it at once place and refer to that in the solid inputs. Now I have this configuration:
Copy code
solids:
  bag_ahn_date:
    inputs:
      bag_cleaned: "bag_cleaned.pandactueelbestaand"
      acquisition_dates: "ahn3.acquisition_dates"
      bag_cleaned_schema: "bag_cleaned"
  bag_ahn_date_index:
    inputs:
      bag_cleaned_schema: "bag_cleaned"
  bag_ahn_overlap:
    inputs:
      bag_cleaned: "bag_cleaned.pandactueelbestaand"
      buffer: "schema_name.buffer_table"
      bag_cleaned_schema: "bag_cleaned"
  bag_ahn_overlap_index:
    inputs:
      bag_cleaned_schema: "bag_cleaned"
And I would like to have a configuration like this one, where the
global
is not a solid, but a way to declare a gobal input parameter
Copy code
solids:
  global:
      bag_cleaned_schema: "bag_cleaned"
  bag_ahn_date:
    inputs:
      bag_cleaned: "bag_cleaned.pandactueelbestaand"
      acquisition_dates: "ahn3.acquisition_dates"
      bag_cleaned_schema: $bag_cleaned_schema
  bag_ahn_date_index:
    inputs:
      bag_cleaned_schema: $bag_cleaned_schema
  bag_ahn_overlap:
    inputs:
      bag_cleaned: "bag_cleaned.pandactueelbestaand"
      buffer: "schema_name.buffer_table"
      bag_cleaned_schema: $bag_cleaned_schema
  bag_ahn_overlap_index:
    inputs:
      bag_cleaned_schema: $bag_cleaned_schema
s
We’re working on a cleaner way of doing it, but I would suggest using a resource to model this.
b
Thank you, I'll look into it!