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
It would be nice if dobi had a way to pass a script that checks own source/artifacts patterns besides the already present local files checks.
For example if i use dobi to deploy some deployment to kubernetes, i'd like to check the dependencies for my deployment, e.g. if something like cert-manager is already present. If the cert-manager is already present, the depends section would be skipped for my deployment.
The resource would be marked fresh when the script returns 0, otherwise the image/job will be build/triggered.
Proposal:
A new property called sources-artifact-job that refers to a dobi job that either fails (returns 1) or succeeds (returns 0).
Example:
meta:
project: testimage=bash:
image=bashtags: [latest]pull: onceimage=checkimage:
image=checkimagetags: [latest]pull: once# this job returns either 0 or 1job=check-dependency-job:
use: checkimagecommand: /check.shjob=dependency-job:
use: bashcommand: /do-something-as-dependency.shsources-artifact-job: check-dependency-jobjob=main-job:
use: bashcommand: /do-something.shdepends: [dependency-job]
The text was updated successfully, but these errors were encountered:
It would be nice if dobi had a way to pass a script that checks own source/artifacts patterns besides the already present local files checks.
For example if i use dobi to deploy some deployment to kubernetes, i'd like to check the dependencies for my deployment, e.g. if something like cert-manager is already present. If the cert-manager is already present, the depends section would be skipped for my deployment.
The resource would be marked fresh when the script returns 0, otherwise the image/job will be build/triggered.
Proposal:
A new property called
sources-artifact-job
that refers to a dobi job that either fails (returns 1) or succeeds (returns 0).Example:
The text was updated successfully, but these errors were encountered: