Variables - ja-guzzle/guzzle_docs GitHub Wiki

Guzzle will support reference of Place holder variables in multiple places. This includes

  1. Global configuration
  2. Module specific configuration at Ingestion,Processing etc
  3. Individual modules configuraation

All the place holder shall use the convention as: @{variable_name}

This is similar to what is being referred by Hive, Spark and others. Guzzle will try to resolve and replace the variable making the parameter values more or less like literal instead of passing them as name=variable pair to underlying engine like Hive or Spark.

If there are unresolved variables they may end up flowing to downstream run time and may or may not get resolved there.

This point there is no prefix or suffix being planned to distinguish guzzle variables from other. Or within guzzle to segregate the system ones with user ones

Open items:

  1. will need update regarding variables framework (the naming convention of variable that we can adopt for system generated one at batch or context columns (location, system etc) , etl stage, job and record level - you saw some example) . most of this can come as place holder as well but the same convention will follow (we don't have any special treatement for system generated and place holder ) in terms of their usage
⚠️ **GitHub.com Fallback** ⚠️