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
The possible action would be define the contracts for the pipelines (input parameters, output parameters) as an example we can use OPA to ensure the specs.
Base pipeline can be re used and only specific steps would be replace per project.
If contract is pre-defined do not need to rely on triggers as the invocation would be the same to all products. We style require specific steps (again with some contract handle with OPA) and move the jsonpath from triggers to umb read messagges.
The text was updated successfully, but these errors were encountered:
The possible action would be define the contracts for the pipelines (input parameters, output parameters) as an example we can use OPA to ensure the specs.
Base pipeline can be re used and only specific steps would be replace per project.
If contract is pre-defined do not need to rely on triggers as the invocation would be the same to all products. We style require specific steps (again with some contract handle with OPA) and move the jsonpath from triggers to umb read messagges.
The text was updated successfully, but these errors were encountered: