You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With this, in the steps settings we could load the step schema as consumer or producer schema from an env variable with the name of the step.
consumer_schema=load(f"schema/{os.env["CONSUMER_SCHEMA"]}_schema")
producer_schema=load(f"schema/{os.env["PRODUCER_SCHEMA"]}_schema")
# this should catch missing consumer or producer schema.
The probleim with this is that we would need to change the build proccess to copy the schema folder as well as the step code.
tareas
....
cambiar los values de los charts para tener las nuevas config
The text was updated successfully, but these errors were encountered:
The idea is to have the output schemas of the steps grouped in a folder inside pipeline monorepo.
ej:
Pipeline
|
| - | schemas
| - |
| - | prv_candidates_schema
| - | xmatch_schema
| - | ...
With this, in the steps settings we could load the step schema as consumer or producer schema from an env variable with the name of the step.
The probleim with this is that we would need to change the build proccess to copy the schema folder as well as the step code.
tareas
....
The text was updated successfully, but these errors were encountered: