dbtcloud.Job
Explore with Pulumi AI
Import
using import blocks (requires Terraform >= 1.5)
import {
to = dbtcloud_job.my_job
id = “job_id”
}
import {
to = dbtcloud_job.my_job
id = “12345”
}
using the older import command
$ pulumi import dbtcloud:index/job:Job my_job "job_id"
$ pulumi import dbtcloud:index/job:Job my_job 12345
Create Job Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new Job(name: string, args: JobArgs, opts?: CustomResourceOptions);
@overload
def Job(resource_name: str,
args: JobArgs,
opts: Optional[ResourceOptions] = None)
@overload
def Job(resource_name: str,
opts: Optional[ResourceOptions] = None,
project_id: Optional[int] = None,
environment_id: Optional[int] = None,
triggers: Optional[JobTriggersArgs] = None,
execute_steps: Optional[Sequence[str]] = None,
self_deferring: Optional[bool] = None,
run_compare_changes: Optional[bool] = None,
errors_on_lint_failure: Optional[bool] = None,
deferring_job_id: Optional[int] = None,
generate_docs: Optional[bool] = None,
is_active: Optional[bool] = None,
job_completion_trigger_conditions: Optional[Sequence[JobJobCompletionTriggerConditionArgs]] = None,
job_type: Optional[str] = None,
dbt_version: Optional[str] = None,
name: Optional[str] = None,
description: Optional[str] = None,
compare_changes_flags: Optional[str] = None,
run_generate_sources: Optional[bool] = None,
run_lint: Optional[bool] = None,
schedule_cron: Optional[str] = None,
schedule_days: Optional[Sequence[int]] = None,
schedule_hours: Optional[Sequence[int]] = None,
schedule_interval: Optional[int] = None,
schedule_type: Optional[str] = None,
num_threads: Optional[int] = None,
target_name: Optional[str] = None,
timeout_seconds: Optional[int] = None,
deferring_environment_id: Optional[int] = None,
triggers_on_draft_pr: Optional[bool] = None)
func NewJob(ctx *Context, name string, args JobArgs, opts ...ResourceOption) (*Job, error)
public Job(string name, JobArgs args, CustomResourceOptions? opts = null)
type: dbtcloud:Job
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args JobArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args JobArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args JobArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args JobArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args JobArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var jobResource = new DbtCloud.Job("jobResource", new()
{
ProjectId = 0,
EnvironmentId = 0,
Triggers = new DbtCloud.Inputs.JobTriggersArgs
{
GitProviderWebhook = false,
GithubWebhook = false,
OnMerge = false,
Schedule = false,
},
ExecuteSteps = new[]
{
"string",
},
SelfDeferring = false,
RunCompareChanges = false,
ErrorsOnLintFailure = false,
DeferringJobId = 0,
GenerateDocs = false,
IsActive = false,
CompletionTriggerCondition = new[]
{
new DbtCloud.Inputs.JobJobCompletionTriggerConditionArgs
{
JobId = 0,
ProjectId = 0,
Statuses = new[]
{
"string",
},
},
},
JobType = "string",
DbtVersion = "string",
Name = "string",
Description = "string",
CompareChangesFlags = "string",
RunGenerateSources = false,
RunLint = false,
ScheduleCron = "string",
ScheduleDays = new[]
{
0,
},
ScheduleHours = new[]
{
0,
},
ScheduleInterval = 0,
ScheduleType = "string",
NumThreads = 0,
TargetName = "string",
DeferringEnvironmentId = 0,
TriggersOnDraftPr = false,
});
example, err := dbtcloud.NewJob(ctx, "jobResource", &dbtcloud.JobArgs{
ProjectId: pulumi.Int(0),
EnvironmentId: pulumi.Int(0),
Triggers: &dbtcloud.JobTriggersArgs{
GitProviderWebhook: pulumi.Bool(false),
GithubWebhook: pulumi.Bool(false),
OnMerge: pulumi.Bool(false),
Schedule: pulumi.Bool(false),
},
ExecuteSteps: pulumi.StringArray{
pulumi.String("string"),
},
SelfDeferring: pulumi.Bool(false),
RunCompareChanges: pulumi.Bool(false),
ErrorsOnLintFailure: pulumi.Bool(false),
DeferringJobId: pulumi.Int(0),
GenerateDocs: pulumi.Bool(false),
IsActive: pulumi.Bool(false),
JobCompletionTriggerConditions: dbtcloud.JobJobCompletionTriggerConditionArray{
&dbtcloud.JobJobCompletionTriggerConditionArgs{
JobId: pulumi.Int(0),
ProjectId: pulumi.Int(0),
Statuses: pulumi.StringArray{
pulumi.String("string"),
},
},
},
JobType: pulumi.String("string"),
DbtVersion: pulumi.String("string"),
Name: pulumi.String("string"),
Description: pulumi.String("string"),
CompareChangesFlags: pulumi.String("string"),
RunGenerateSources: pulumi.Bool(false),
RunLint: pulumi.Bool(false),
ScheduleCron: pulumi.String("string"),
ScheduleDays: pulumi.IntArray{
pulumi.Int(0),
},
ScheduleHours: pulumi.IntArray{
pulumi.Int(0),
},
ScheduleInterval: pulumi.Int(0),
ScheduleType: pulumi.String("string"),
NumThreads: pulumi.Int(0),
TargetName: pulumi.String("string"),
DeferringEnvironmentId: pulumi.Int(0),
TriggersOnDraftPr: pulumi.Bool(false),
})
var jobResource = new Job("jobResource", JobArgs.builder()
.projectId(0)
.environmentId(0)
.triggers(JobTriggersArgs.builder()
.gitProviderWebhook(false)
.githubWebhook(false)
.onMerge(false)
.schedule(false)
.build())
.executeSteps("string")
.selfDeferring(false)
.runCompareChanges(false)
.errorsOnLintFailure(false)
.deferringJobId(0)
.generateDocs(false)
.isActive(false)
.jobCompletionTriggerConditions(JobJobCompletionTriggerConditionArgs.builder()
.jobId(0)
.projectId(0)
.statuses("string")
.build())
.jobType("string")
.dbtVersion("string")
.name("string")
.description("string")
.compareChangesFlags("string")
.runGenerateSources(false)
.runLint(false)
.scheduleCron("string")
.scheduleDays(0)
.scheduleHours(0)
.scheduleInterval(0)
.scheduleType("string")
.numThreads(0)
.targetName("string")
.deferringEnvironmentId(0)
.triggersOnDraftPr(false)
.build());
job_resource = dbtcloud.Job("jobResource",
project_id=0,
environment_id=0,
triggers={
"git_provider_webhook": False,
"github_webhook": False,
"on_merge": False,
"schedule": False,
},
execute_steps=["string"],
self_deferring=False,
run_compare_changes=False,
errors_on_lint_failure=False,
deferring_job_id=0,
generate_docs=False,
is_active=False,
job_completion_trigger_conditions=[{
"job_id": 0,
"project_id": 0,
"statuses": ["string"],
}],
job_type="string",
dbt_version="string",
name="string",
description="string",
compare_changes_flags="string",
run_generate_sources=False,
run_lint=False,
schedule_cron="string",
schedule_days=[0],
schedule_hours=[0],
schedule_interval=0,
schedule_type="string",
num_threads=0,
target_name="string",
deferring_environment_id=0,
triggers_on_draft_pr=False)
const jobResource = new dbtcloud.Job("jobResource", {
projectId: 0,
environmentId: 0,
triggers: {
gitProviderWebhook: false,
githubWebhook: false,
onMerge: false,
schedule: false,
},
executeSteps: ["string"],
selfDeferring: false,
runCompareChanges: false,
errorsOnLintFailure: false,
deferringJobId: 0,
generateDocs: false,
isActive: false,
jobCompletionTriggerConditions: [{
jobId: 0,
projectId: 0,
statuses: ["string"],
}],
jobType: "string",
dbtVersion: "string",
name: "string",
description: "string",
compareChangesFlags: "string",
runGenerateSources: false,
runLint: false,
scheduleCron: "string",
scheduleDays: [0],
scheduleHours: [0],
scheduleInterval: 0,
scheduleType: "string",
numThreads: 0,
targetName: "string",
deferringEnvironmentId: 0,
triggersOnDraftPr: false,
});
type: dbtcloud:Job
properties:
compareChangesFlags: string
dbtVersion: string
deferringEnvironmentId: 0
deferringJobId: 0
description: string
environmentId: 0
errorsOnLintFailure: false
executeSteps:
- string
generateDocs: false
isActive: false
jobCompletionTriggerConditions:
- jobId: 0
projectId: 0
statuses:
- string
jobType: string
name: string
numThreads: 0
projectId: 0
runCompareChanges: false
runGenerateSources: false
runLint: false
scheduleCron: string
scheduleDays:
- 0
scheduleHours:
- 0
scheduleInterval: 0
scheduleType: string
selfDeferring: false
targetName: string
triggers:
gitProviderWebhook: false
githubWebhook: false
onMerge: false
schedule: false
triggersOnDraftPr: false
Job Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The Job resource accepts the following input properties:
- Environment
Id int - Environment ID to create the job in
- Execute
Steps List<string> - List of commands to execute for the job
- Project
Id int - Project ID to create the job in
- Triggers
Pulumi.
Dbt Cloud. Inputs. Job Triggers - Flags for which types of triggers to use, the values are
github_webhook
,git_provider_webhook
,schedule
andon_merge
. All flags should be listed and set withtrue
orfalse
. Whenon_merge
istrue
, all the other values must be false.\n\ncustom_branch_only
used to be allowed but has been deprecated from the API. The jobs will use the custom branch of the environment. Please remove thecustom_branch_only
from your config. \n\nTo create a job in a 'deactivated' state, set all tofalse
. - Compare
Changes stringFlags - The model selector for checking changes in the compare changes Advanced CI feature
- Completion
Trigger List<Pulumi.Condition Dbt Cloud. Inputs. Job Job Completion Trigger Condition> - Which other job should trigger this job when it finishes, and on which conditions (sometimes referred as 'job chaining').
- Dbt
Version string - Version number of dbt to use in this job, usually in the format 1.2.0-latest rather than core versions
- Deferring
Environment intId - Environment identifier that this job defers to (new deferring approach)
- Deferring
Job intId - Job identifier that this job defers to (legacy deferring approach)
- Description string
- Description for the job
- Errors
On boolLint Failure - Whether the CI job should fail when a lint error is found. Only used when
run_lint
is set totrue
. Defaults totrue
. - Generate
Docs bool - Flag for whether the job should generate documentation
- Is
Active bool - Should always be set to true as setting it to false is the same as creating a job in a deleted state. To create/keep a job in a 'deactivated' state, check the
triggers
config. - Job
Type string - Can be used to enforce the job type betwen
ci
,merge
andscheduled
. Without this value the job type is inferred from the triggers configured - Name string
- Job name
- Num
Threads int - Number of threads to use in the job
- Run
Compare boolChanges - Whether the CI job should compare data changes introduced by the code changes. Requires
deferring_environment_id
to be set. (Advanced CI needs to be activated in the dbt Cloud Account Settings first as well) - Run
Generate boolSources - Flag for whether the job should add a
dbt source freshness
step to the job. The difference between manually adding a step withdbt source freshness
in the job steps or using this flag is that with this flag, a failed freshness will still allow the following steps to run. - Run
Lint bool - Whether the CI job should lint SQL changes. Defaults to
false
. - Schedule
Cron string - Custom cron expression for schedule
- Schedule
Days List<int> - List of days of week as numbers (0 = Sunday, 7 = Saturday) to execute the job at if running on a schedule
- Schedule
Hours List<int> - List of hours to execute the job at if running on a schedule
- Schedule
Interval int - Number of hours between job executions if running on a schedule
- Schedule
Type string - Type of schedule to use, one of everyday/ daysofweek/ customcron/ interval_cron
- Self
Deferring bool - Whether this job defers on a previous run of itself
- Target
Name string - Target name for the dbt profile
- Timeout
Seconds int - [Deprectated - Moved to execution.timeout_seconds] Number of seconds to allow the job to run before timing out
- Triggers
On boolDraft Pr - Whether the CI job should be automatically triggered on draft PRs
- Environment
Id int - Environment ID to create the job in
- Execute
Steps []string - List of commands to execute for the job
- Project
Id int - Project ID to create the job in
- Triggers
Job
Triggers Args - Flags for which types of triggers to use, the values are
github_webhook
,git_provider_webhook
,schedule
andon_merge
. All flags should be listed and set withtrue
orfalse
. Whenon_merge
istrue
, all the other values must be false.\n\ncustom_branch_only
used to be allowed but has been deprecated from the API. The jobs will use the custom branch of the environment. Please remove thecustom_branch_only
from your config. \n\nTo create a job in a 'deactivated' state, set all tofalse
. - Compare
Changes stringFlags - The model selector for checking changes in the compare changes Advanced CI feature
- Dbt
Version string - Version number of dbt to use in this job, usually in the format 1.2.0-latest rather than core versions
- Deferring
Environment intId - Environment identifier that this job defers to (new deferring approach)
- Deferring
Job intId - Job identifier that this job defers to (legacy deferring approach)
- Description string
- Description for the job
- Errors
On boolLint Failure - Whether the CI job should fail when a lint error is found. Only used when
run_lint
is set totrue
. Defaults totrue
. - Generate
Docs bool - Flag for whether the job should generate documentation
- Is
Active bool - Should always be set to true as setting it to false is the same as creating a job in a deleted state. To create/keep a job in a 'deactivated' state, check the
triggers
config. - Job
Completion []JobTrigger Conditions Job Completion Trigger Condition Args - Which other job should trigger this job when it finishes, and on which conditions (sometimes referred as 'job chaining').
- Job
Type string - Can be used to enforce the job type betwen
ci
,merge
andscheduled
. Without this value the job type is inferred from the triggers configured - Name string
- Job name
- Num
Threads int - Number of threads to use in the job
- Run
Compare boolChanges - Whether the CI job should compare data changes introduced by the code changes. Requires
deferring_environment_id
to be set. (Advanced CI needs to be activated in the dbt Cloud Account Settings first as well) - Run
Generate boolSources - Flag for whether the job should add a
dbt source freshness
step to the job. The difference between manually adding a step withdbt source freshness
in the job steps or using this flag is that with this flag, a failed freshness will still allow the following steps to run. - Run
Lint bool - Whether the CI job should lint SQL changes. Defaults to
false
. - Schedule
Cron string - Custom cron expression for schedule
- Schedule
Days []int - List of days of week as numbers (0 = Sunday, 7 = Saturday) to execute the job at if running on a schedule
- Schedule
Hours []int - List of hours to execute the job at if running on a schedule
- Schedule
Interval int - Number of hours between job executions if running on a schedule
- Schedule
Type string - Type of schedule to use, one of everyday/ daysofweek/ customcron/ interval_cron
- Self
Deferring bool - Whether this job defers on a previous run of itself
- Target
Name string - Target name for the dbt profile
- Timeout
Seconds int - [Deprectated - Moved to execution.timeout_seconds] Number of seconds to allow the job to run before timing out
- Triggers
On boolDraft Pr - Whether the CI job should be automatically triggered on draft PRs
- environment
Id Integer - Environment ID to create the job in
- execute
Steps List<String> - List of commands to execute for the job
- project
Id Integer - Project ID to create the job in
- triggers
Job
Triggers - Flags for which types of triggers to use, the values are
github_webhook
,git_provider_webhook
,schedule
andon_merge
. All flags should be listed and set withtrue
orfalse
. Whenon_merge
istrue
, all the other values must be false.\n\ncustom_branch_only
used to be allowed but has been deprecated from the API. The jobs will use the custom branch of the environment. Please remove thecustom_branch_only
from your config. \n\nTo create a job in a 'deactivated' state, set all tofalse
. - compare
Changes StringFlags - The model selector for checking changes in the compare changes Advanced CI feature
- dbt
Version String - Version number of dbt to use in this job, usually in the format 1.2.0-latest rather than core versions
- deferring
Environment IntegerId - Environment identifier that this job defers to (new deferring approach)
- deferring
Job IntegerId - Job identifier that this job defers to (legacy deferring approach)
- description String
- Description for the job
- errors
On BooleanLint Failure - Whether the CI job should fail when a lint error is found. Only used when
run_lint
is set totrue
. Defaults totrue
. - generate
Docs Boolean - Flag for whether the job should generate documentation
- is
Active Boolean - Should always be set to true as setting it to false is the same as creating a job in a deleted state. To create/keep a job in a 'deactivated' state, check the
triggers
config. - job
Completion List<JobTrigger Conditions Job Completion Trigger Condition> - Which other job should trigger this job when it finishes, and on which conditions (sometimes referred as 'job chaining').
- job
Type String - Can be used to enforce the job type betwen
ci
,merge
andscheduled
. Without this value the job type is inferred from the triggers configured - name String
- Job name
- num
Threads Integer - Number of threads to use in the job
- run
Compare BooleanChanges - Whether the CI job should compare data changes introduced by the code changes. Requires
deferring_environment_id
to be set. (Advanced CI needs to be activated in the dbt Cloud Account Settings first as well) - run
Generate BooleanSources - Flag for whether the job should add a
dbt source freshness
step to the job. The difference between manually adding a step withdbt source freshness
in the job steps or using this flag is that with this flag, a failed freshness will still allow the following steps to run. - run
Lint Boolean - Whether the CI job should lint SQL changes. Defaults to
false
. - schedule
Cron String - Custom cron expression for schedule
- schedule
Days List<Integer> - List of days of week as numbers (0 = Sunday, 7 = Saturday) to execute the job at if running on a schedule
- schedule
Hours List<Integer> - List of hours to execute the job at if running on a schedule
- schedule
Interval Integer - Number of hours between job executions if running on a schedule
- schedule
Type String - Type of schedule to use, one of everyday/ daysofweek/ customcron/ interval_cron
- self
Deferring Boolean - Whether this job defers on a previous run of itself
- target
Name String - Target name for the dbt profile
- timeout
Seconds Integer - [Deprectated - Moved to execution.timeout_seconds] Number of seconds to allow the job to run before timing out
- triggers
On BooleanDraft Pr - Whether the CI job should be automatically triggered on draft PRs
- environment
Id number - Environment ID to create the job in
- execute
Steps string[] - List of commands to execute for the job
- project
Id number - Project ID to create the job in
- triggers
Job
Triggers - Flags for which types of triggers to use, the values are
github_webhook
,git_provider_webhook
,schedule
andon_merge
. All flags should be listed and set withtrue
orfalse
. Whenon_merge
istrue
, all the other values must be false.\n\ncustom_branch_only
used to be allowed but has been deprecated from the API. The jobs will use the custom branch of the environment. Please remove thecustom_branch_only
from your config. \n\nTo create a job in a 'deactivated' state, set all tofalse
. - compare
Changes stringFlags - The model selector for checking changes in the compare changes Advanced CI feature
- dbt
Version string - Version number of dbt to use in this job, usually in the format 1.2.0-latest rather than core versions
- deferring
Environment numberId - Environment identifier that this job defers to (new deferring approach)
- deferring
Job numberId - Job identifier that this job defers to (legacy deferring approach)
- description string
- Description for the job
- errors
On booleanLint Failure - Whether the CI job should fail when a lint error is found. Only used when
run_lint
is set totrue
. Defaults totrue
. - generate
Docs boolean - Flag for whether the job should generate documentation
- is
Active boolean - Should always be set to true as setting it to false is the same as creating a job in a deleted state. To create/keep a job in a 'deactivated' state, check the
triggers
config. - job
Completion JobTrigger Conditions Job Completion Trigger Condition[] - Which other job should trigger this job when it finishes, and on which conditions (sometimes referred as 'job chaining').
- job
Type string - Can be used to enforce the job type betwen
ci
,merge
andscheduled
. Without this value the job type is inferred from the triggers configured - name string
- Job name
- num
Threads number - Number of threads to use in the job
- run
Compare booleanChanges - Whether the CI job should compare data changes introduced by the code changes. Requires
deferring_environment_id
to be set. (Advanced CI needs to be activated in the dbt Cloud Account Settings first as well) - run
Generate booleanSources - Flag for whether the job should add a
dbt source freshness
step to the job. The difference between manually adding a step withdbt source freshness
in the job steps or using this flag is that with this flag, a failed freshness will still allow the following steps to run. - run
Lint boolean - Whether the CI job should lint SQL changes. Defaults to
false
. - schedule
Cron string - Custom cron expression for schedule
- schedule
Days number[] - List of days of week as numbers (0 = Sunday, 7 = Saturday) to execute the job at if running on a schedule
- schedule
Hours number[] - List of hours to execute the job at if running on a schedule
- schedule
Interval number - Number of hours between job executions if running on a schedule
- schedule
Type string - Type of schedule to use, one of everyday/ daysofweek/ customcron/ interval_cron
- self
Deferring boolean - Whether this job defers on a previous run of itself
- target
Name string - Target name for the dbt profile
- timeout
Seconds number - [Deprectated - Moved to execution.timeout_seconds] Number of seconds to allow the job to run before timing out
- triggers
On booleanDraft Pr - Whether the CI job should be automatically triggered on draft PRs
- environment_
id int - Environment ID to create the job in
- execute_
steps Sequence[str] - List of commands to execute for the job
- project_
id int - Project ID to create the job in
- triggers
Job
Triggers Args - Flags for which types of triggers to use, the values are
github_webhook
,git_provider_webhook
,schedule
andon_merge
. All flags should be listed and set withtrue
orfalse
. Whenon_merge
istrue
, all the other values must be false.\n\ncustom_branch_only
used to be allowed but has been deprecated from the API. The jobs will use the custom branch of the environment. Please remove thecustom_branch_only
from your config. \n\nTo create a job in a 'deactivated' state, set all tofalse
. - compare_
changes_ strflags - The model selector for checking changes in the compare changes Advanced CI feature
- dbt_
version str - Version number of dbt to use in this job, usually in the format 1.2.0-latest rather than core versions
- deferring_
environment_ intid - Environment identifier that this job defers to (new deferring approach)
- deferring_
job_ intid - Job identifier that this job defers to (legacy deferring approach)
- description str
- Description for the job
- errors_
on_ boollint_ failure - Whether the CI job should fail when a lint error is found. Only used when
run_lint
is set totrue
. Defaults totrue
. - generate_
docs bool - Flag for whether the job should generate documentation
- is_
active bool - Should always be set to true as setting it to false is the same as creating a job in a deleted state. To create/keep a job in a 'deactivated' state, check the
triggers
config. - job_
completion_ Sequence[Jobtrigger_ conditions Job Completion Trigger Condition Args] - Which other job should trigger this job when it finishes, and on which conditions (sometimes referred as 'job chaining').
- job_
type str - Can be used to enforce the job type betwen
ci
,merge
andscheduled
. Without this value the job type is inferred from the triggers configured - name str
- Job name
- num_
threads int - Number of threads to use in the job
- run_
compare_ boolchanges - Whether the CI job should compare data changes introduced by the code changes. Requires
deferring_environment_id
to be set. (Advanced CI needs to be activated in the dbt Cloud Account Settings first as well) - run_
generate_ boolsources - Flag for whether the job should add a
dbt source freshness
step to the job. The difference between manually adding a step withdbt source freshness
in the job steps or using this flag is that with this flag, a failed freshness will still allow the following steps to run. - run_
lint bool - Whether the CI job should lint SQL changes. Defaults to
false
. - schedule_
cron str - Custom cron expression for schedule
- schedule_
days Sequence[int] - List of days of week as numbers (0 = Sunday, 7 = Saturday) to execute the job at if running on a schedule
- schedule_
hours Sequence[int] - List of hours to execute the job at if running on a schedule
- schedule_
interval int - Number of hours between job executions if running on a schedule
- schedule_
type str - Type of schedule to use, one of everyday/ daysofweek/ customcron/ interval_cron
- self_
deferring bool - Whether this job defers on a previous run of itself
- target_
name str - Target name for the dbt profile
- timeout_
seconds int - [Deprectated - Moved to execution.timeout_seconds] Number of seconds to allow the job to run before timing out
- triggers_
on_ booldraft_ pr - Whether the CI job should be automatically triggered on draft PRs
- environment
Id Number - Environment ID to create the job in
- execute
Steps List<String> - List of commands to execute for the job
- project
Id Number - Project ID to create the job in
- triggers Property Map
- Flags for which types of triggers to use, the values are
github_webhook
,git_provider_webhook
,schedule
andon_merge
. All flags should be listed and set withtrue
orfalse
. Whenon_merge
istrue
, all the other values must be false.\n\ncustom_branch_only
used to be allowed but has been deprecated from the API. The jobs will use the custom branch of the environment. Please remove thecustom_branch_only
from your config. \n\nTo create a job in a 'deactivated' state, set all tofalse
. - compare
Changes StringFlags - The model selector for checking changes in the compare changes Advanced CI feature
- dbt
Version String - Version number of dbt to use in this job, usually in the format 1.2.0-latest rather than core versions
- deferring
Environment NumberId - Environment identifier that this job defers to (new deferring approach)
- deferring
Job NumberId - Job identifier that this job defers to (legacy deferring approach)
- description String
- Description for the job
- errors
On BooleanLint Failure - Whether the CI job should fail when a lint error is found. Only used when
run_lint
is set totrue
. Defaults totrue
. - generate
Docs Boolean - Flag for whether the job should generate documentation
- is
Active Boolean - Should always be set to true as setting it to false is the same as creating a job in a deleted state. To create/keep a job in a 'deactivated' state, check the
triggers
config. - job
Completion List<Property Map>Trigger Conditions - Which other job should trigger this job when it finishes, and on which conditions (sometimes referred as 'job chaining').
- job
Type String - Can be used to enforce the job type betwen
ci
,merge
andscheduled
. Without this value the job type is inferred from the triggers configured - name String
- Job name
- num
Threads Number - Number of threads to use in the job
- run
Compare BooleanChanges - Whether the CI job should compare data changes introduced by the code changes. Requires
deferring_environment_id
to be set. (Advanced CI needs to be activated in the dbt Cloud Account Settings first as well) - run
Generate BooleanSources - Flag for whether the job should add a
dbt source freshness
step to the job. The difference between manually adding a step withdbt source freshness
in the job steps or using this flag is that with this flag, a failed freshness will still allow the following steps to run. - run
Lint Boolean - Whether the CI job should lint SQL changes. Defaults to
false
. - schedule
Cron String - Custom cron expression for schedule
- schedule
Days List<Number> - List of days of week as numbers (0 = Sunday, 7 = Saturday) to execute the job at if running on a schedule
- schedule
Hours List<Number> - List of hours to execute the job at if running on a schedule
- schedule
Interval Number - Number of hours between job executions if running on a schedule
- schedule
Type String - Type of schedule to use, one of everyday/ daysofweek/ customcron/ interval_cron
- self
Deferring Boolean - Whether this job defers on a previous run of itself
- target
Name String - Target name for the dbt profile
- timeout
Seconds Number - [Deprectated - Moved to execution.timeout_seconds] Number of seconds to allow the job to run before timing out
- triggers
On BooleanDraft Pr - Whether the CI job should be automatically triggered on draft PRs
Outputs
All input properties are implicitly available as output properties. Additionally, the Job resource produces the following output properties:
Look up Existing Job Resource
Get an existing Job resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: JobState, opts?: CustomResourceOptions): Job
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
compare_changes_flags: Optional[str] = None,
dbt_version: Optional[str] = None,
deferring_environment_id: Optional[int] = None,
deferring_job_id: Optional[int] = None,
description: Optional[str] = None,
environment_id: Optional[int] = None,
errors_on_lint_failure: Optional[bool] = None,
execute_steps: Optional[Sequence[str]] = None,
generate_docs: Optional[bool] = None,
is_active: Optional[bool] = None,
job_completion_trigger_conditions: Optional[Sequence[JobJobCompletionTriggerConditionArgs]] = None,
job_id: Optional[int] = None,
job_type: Optional[str] = None,
name: Optional[str] = None,
num_threads: Optional[int] = None,
project_id: Optional[int] = None,
run_compare_changes: Optional[bool] = None,
run_generate_sources: Optional[bool] = None,
run_lint: Optional[bool] = None,
schedule_cron: Optional[str] = None,
schedule_days: Optional[Sequence[int]] = None,
schedule_hours: Optional[Sequence[int]] = None,
schedule_interval: Optional[int] = None,
schedule_type: Optional[str] = None,
self_deferring: Optional[bool] = None,
target_name: Optional[str] = None,
timeout_seconds: Optional[int] = None,
triggers: Optional[JobTriggersArgs] = None,
triggers_on_draft_pr: Optional[bool] = None) -> Job
func GetJob(ctx *Context, name string, id IDInput, state *JobState, opts ...ResourceOption) (*Job, error)
public static Job Get(string name, Input<string> id, JobState? state, CustomResourceOptions? opts = null)
public static Job get(String name, Output<String> id, JobState state, CustomResourceOptions options)
resources: _: type: dbtcloud:Job get: id: ${id}
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- Compare
Changes stringFlags - The model selector for checking changes in the compare changes Advanced CI feature
- Completion
Trigger List<Pulumi.Condition Dbt Cloud. Inputs. Job Job Completion Trigger Condition> - Which other job should trigger this job when it finishes, and on which conditions (sometimes referred as 'job chaining').
- Dbt
Version string - Version number of dbt to use in this job, usually in the format 1.2.0-latest rather than core versions
- Deferring
Environment intId - Environment identifier that this job defers to (new deferring approach)
- Deferring
Job intId - Job identifier that this job defers to (legacy deferring approach)
- Description string
- Description for the job
- Environment
Id int - Environment ID to create the job in
- Errors
On boolLint Failure - Whether the CI job should fail when a lint error is found. Only used when
run_lint
is set totrue
. Defaults totrue
. - Execute
Steps List<string> - List of commands to execute for the job
- Generate
Docs bool - Flag for whether the job should generate documentation
- Is
Active bool - Should always be set to true as setting it to false is the same as creating a job in a deleted state. To create/keep a job in a 'deactivated' state, check the
triggers
config. - Job
Id int - Job identifier
- Job
Type string - Can be used to enforce the job type betwen
ci
,merge
andscheduled
. Without this value the job type is inferred from the triggers configured - Name string
- Job name
- Num
Threads int - Number of threads to use in the job
- Project
Id int - Project ID to create the job in
- Run
Compare boolChanges - Whether the CI job should compare data changes introduced by the code changes. Requires
deferring_environment_id
to be set. (Advanced CI needs to be activated in the dbt Cloud Account Settings first as well) - Run
Generate boolSources - Flag for whether the job should add a
dbt source freshness
step to the job. The difference between manually adding a step withdbt source freshness
in the job steps or using this flag is that with this flag, a failed freshness will still allow the following steps to run. - Run
Lint bool - Whether the CI job should lint SQL changes. Defaults to
false
. - Schedule
Cron string - Custom cron expression for schedule
- Schedule
Days List<int> - List of days of week as numbers (0 = Sunday, 7 = Saturday) to execute the job at if running on a schedule
- Schedule
Hours List<int> - List of hours to execute the job at if running on a schedule
- Schedule
Interval int - Number of hours between job executions if running on a schedule
- Schedule
Type string - Type of schedule to use, one of everyday/ daysofweek/ customcron/ interval_cron
- Self
Deferring bool - Whether this job defers on a previous run of itself
- Target
Name string - Target name for the dbt profile
- Timeout
Seconds int - [Deprectated - Moved to execution.timeout_seconds] Number of seconds to allow the job to run before timing out
- Triggers
Pulumi.
Dbt Cloud. Inputs. Job Triggers - Flags for which types of triggers to use, the values are
github_webhook
,git_provider_webhook
,schedule
andon_merge
. All flags should be listed and set withtrue
orfalse
. Whenon_merge
istrue
, all the other values must be false.\n\ncustom_branch_only
used to be allowed but has been deprecated from the API. The jobs will use the custom branch of the environment. Please remove thecustom_branch_only
from your config. \n\nTo create a job in a 'deactivated' state, set all tofalse
. - Triggers
On boolDraft Pr - Whether the CI job should be automatically triggered on draft PRs
- Compare
Changes stringFlags - The model selector for checking changes in the compare changes Advanced CI feature
- Dbt
Version string - Version number of dbt to use in this job, usually in the format 1.2.0-latest rather than core versions
- Deferring
Environment intId - Environment identifier that this job defers to (new deferring approach)
- Deferring
Job intId - Job identifier that this job defers to (legacy deferring approach)
- Description string
- Description for the job
- Environment
Id int - Environment ID to create the job in
- Errors
On boolLint Failure - Whether the CI job should fail when a lint error is found. Only used when
run_lint
is set totrue
. Defaults totrue
. - Execute
Steps []string - List of commands to execute for the job
- Generate
Docs bool - Flag for whether the job should generate documentation
- Is
Active bool - Should always be set to true as setting it to false is the same as creating a job in a deleted state. To create/keep a job in a 'deactivated' state, check the
triggers
config. - Job
Completion []JobTrigger Conditions Job Completion Trigger Condition Args - Which other job should trigger this job when it finishes, and on which conditions (sometimes referred as 'job chaining').
- Job
Id int - Job identifier
- Job
Type string - Can be used to enforce the job type betwen
ci
,merge
andscheduled
. Without this value the job type is inferred from the triggers configured - Name string
- Job name
- Num
Threads int - Number of threads to use in the job
- Project
Id int - Project ID to create the job in
- Run
Compare boolChanges - Whether the CI job should compare data changes introduced by the code changes. Requires
deferring_environment_id
to be set. (Advanced CI needs to be activated in the dbt Cloud Account Settings first as well) - Run
Generate boolSources - Flag for whether the job should add a
dbt source freshness
step to the job. The difference between manually adding a step withdbt source freshness
in the job steps or using this flag is that with this flag, a failed freshness will still allow the following steps to run. - Run
Lint bool - Whether the CI job should lint SQL changes. Defaults to
false
. - Schedule
Cron string - Custom cron expression for schedule
- Schedule
Days []int - List of days of week as numbers (0 = Sunday, 7 = Saturday) to execute the job at if running on a schedule
- Schedule
Hours []int - List of hours to execute the job at if running on a schedule
- Schedule
Interval int - Number of hours between job executions if running on a schedule
- Schedule
Type string - Type of schedule to use, one of everyday/ daysofweek/ customcron/ interval_cron
- Self
Deferring bool - Whether this job defers on a previous run of itself
- Target
Name string - Target name for the dbt profile
- Timeout
Seconds int - [Deprectated - Moved to execution.timeout_seconds] Number of seconds to allow the job to run before timing out
- Triggers
Job
Triggers Args - Flags for which types of triggers to use, the values are
github_webhook
,git_provider_webhook
,schedule
andon_merge
. All flags should be listed and set withtrue
orfalse
. Whenon_merge
istrue
, all the other values must be false.\n\ncustom_branch_only
used to be allowed but has been deprecated from the API. The jobs will use the custom branch of the environment. Please remove thecustom_branch_only
from your config. \n\nTo create a job in a 'deactivated' state, set all tofalse
. - Triggers
On boolDraft Pr - Whether the CI job should be automatically triggered on draft PRs
- compare
Changes StringFlags - The model selector for checking changes in the compare changes Advanced CI feature
- dbt
Version String - Version number of dbt to use in this job, usually in the format 1.2.0-latest rather than core versions
- deferring
Environment IntegerId - Environment identifier that this job defers to (new deferring approach)
- deferring
Job IntegerId - Job identifier that this job defers to (legacy deferring approach)
- description String
- Description for the job
- environment
Id Integer - Environment ID to create the job in
- errors
On BooleanLint Failure - Whether the CI job should fail when a lint error is found. Only used when
run_lint
is set totrue
. Defaults totrue
. - execute
Steps List<String> - List of commands to execute for the job
- generate
Docs Boolean - Flag for whether the job should generate documentation
- is
Active Boolean - Should always be set to true as setting it to false is the same as creating a job in a deleted state. To create/keep a job in a 'deactivated' state, check the
triggers
config. - job
Completion List<JobTrigger Conditions Job Completion Trigger Condition> - Which other job should trigger this job when it finishes, and on which conditions (sometimes referred as 'job chaining').
- job
Id Integer - Job identifier
- job
Type String - Can be used to enforce the job type betwen
ci
,merge
andscheduled
. Without this value the job type is inferred from the triggers configured - name String
- Job name
- num
Threads Integer - Number of threads to use in the job
- project
Id Integer - Project ID to create the job in
- run
Compare BooleanChanges - Whether the CI job should compare data changes introduced by the code changes. Requires
deferring_environment_id
to be set. (Advanced CI needs to be activated in the dbt Cloud Account Settings first as well) - run
Generate BooleanSources - Flag for whether the job should add a
dbt source freshness
step to the job. The difference between manually adding a step withdbt source freshness
in the job steps or using this flag is that with this flag, a failed freshness will still allow the following steps to run. - run
Lint Boolean - Whether the CI job should lint SQL changes. Defaults to
false
. - schedule
Cron String - Custom cron expression for schedule
- schedule
Days List<Integer> - List of days of week as numbers (0 = Sunday, 7 = Saturday) to execute the job at if running on a schedule
- schedule
Hours List<Integer> - List of hours to execute the job at if running on a schedule
- schedule
Interval Integer - Number of hours between job executions if running on a schedule
- schedule
Type String - Type of schedule to use, one of everyday/ daysofweek/ customcron/ interval_cron
- self
Deferring Boolean - Whether this job defers on a previous run of itself
- target
Name String - Target name for the dbt profile
- timeout
Seconds Integer - [Deprectated - Moved to execution.timeout_seconds] Number of seconds to allow the job to run before timing out
- triggers
Job
Triggers - Flags for which types of triggers to use, the values are
github_webhook
,git_provider_webhook
,schedule
andon_merge
. All flags should be listed and set withtrue
orfalse
. Whenon_merge
istrue
, all the other values must be false.\n\ncustom_branch_only
used to be allowed but has been deprecated from the API. The jobs will use the custom branch of the environment. Please remove thecustom_branch_only
from your config. \n\nTo create a job in a 'deactivated' state, set all tofalse
. - triggers
On BooleanDraft Pr - Whether the CI job should be automatically triggered on draft PRs
- compare
Changes stringFlags - The model selector for checking changes in the compare changes Advanced CI feature
- dbt
Version string - Version number of dbt to use in this job, usually in the format 1.2.0-latest rather than core versions
- deferring
Environment numberId - Environment identifier that this job defers to (new deferring approach)
- deferring
Job numberId - Job identifier that this job defers to (legacy deferring approach)
- description string
- Description for the job
- environment
Id number - Environment ID to create the job in
- errors
On booleanLint Failure - Whether the CI job should fail when a lint error is found. Only used when
run_lint
is set totrue
. Defaults totrue
. - execute
Steps string[] - List of commands to execute for the job
- generate
Docs boolean - Flag for whether the job should generate documentation
- is
Active boolean - Should always be set to true as setting it to false is the same as creating a job in a deleted state. To create/keep a job in a 'deactivated' state, check the
triggers
config. - job
Completion JobTrigger Conditions Job Completion Trigger Condition[] - Which other job should trigger this job when it finishes, and on which conditions (sometimes referred as 'job chaining').
- job
Id number - Job identifier
- job
Type string - Can be used to enforce the job type betwen
ci
,merge
andscheduled
. Without this value the job type is inferred from the triggers configured - name string
- Job name
- num
Threads number - Number of threads to use in the job
- project
Id number - Project ID to create the job in
- run
Compare booleanChanges - Whether the CI job should compare data changes introduced by the code changes. Requires
deferring_environment_id
to be set. (Advanced CI needs to be activated in the dbt Cloud Account Settings first as well) - run
Generate booleanSources - Flag for whether the job should add a
dbt source freshness
step to the job. The difference between manually adding a step withdbt source freshness
in the job steps or using this flag is that with this flag, a failed freshness will still allow the following steps to run. - run
Lint boolean - Whether the CI job should lint SQL changes. Defaults to
false
. - schedule
Cron string - Custom cron expression for schedule
- schedule
Days number[] - List of days of week as numbers (0 = Sunday, 7 = Saturday) to execute the job at if running on a schedule
- schedule
Hours number[] - List of hours to execute the job at if running on a schedule
- schedule
Interval number - Number of hours between job executions if running on a schedule
- schedule
Type string - Type of schedule to use, one of everyday/ daysofweek/ customcron/ interval_cron
- self
Deferring boolean - Whether this job defers on a previous run of itself
- target
Name string - Target name for the dbt profile
- timeout
Seconds number - [Deprectated - Moved to execution.timeout_seconds] Number of seconds to allow the job to run before timing out
- triggers
Job
Triggers - Flags for which types of triggers to use, the values are
github_webhook
,git_provider_webhook
,schedule
andon_merge
. All flags should be listed and set withtrue
orfalse
. Whenon_merge
istrue
, all the other values must be false.\n\ncustom_branch_only
used to be allowed but has been deprecated from the API. The jobs will use the custom branch of the environment. Please remove thecustom_branch_only
from your config. \n\nTo create a job in a 'deactivated' state, set all tofalse
. - triggers
On booleanDraft Pr - Whether the CI job should be automatically triggered on draft PRs
- compare_
changes_ strflags - The model selector for checking changes in the compare changes Advanced CI feature
- dbt_
version str - Version number of dbt to use in this job, usually in the format 1.2.0-latest rather than core versions
- deferring_
environment_ intid - Environment identifier that this job defers to (new deferring approach)
- deferring_
job_ intid - Job identifier that this job defers to (legacy deferring approach)
- description str
- Description for the job
- environment_
id int - Environment ID to create the job in
- errors_
on_ boollint_ failure - Whether the CI job should fail when a lint error is found. Only used when
run_lint
is set totrue
. Defaults totrue
. - execute_
steps Sequence[str] - List of commands to execute for the job
- generate_
docs bool - Flag for whether the job should generate documentation
- is_
active bool - Should always be set to true as setting it to false is the same as creating a job in a deleted state. To create/keep a job in a 'deactivated' state, check the
triggers
config. - job_
completion_ Sequence[Jobtrigger_ conditions Job Completion Trigger Condition Args] - Which other job should trigger this job when it finishes, and on which conditions (sometimes referred as 'job chaining').
- job_
id int - Job identifier
- job_
type str - Can be used to enforce the job type betwen
ci
,merge
andscheduled
. Without this value the job type is inferred from the triggers configured - name str
- Job name
- num_
threads int - Number of threads to use in the job
- project_
id int - Project ID to create the job in
- run_
compare_ boolchanges - Whether the CI job should compare data changes introduced by the code changes. Requires
deferring_environment_id
to be set. (Advanced CI needs to be activated in the dbt Cloud Account Settings first as well) - run_
generate_ boolsources - Flag for whether the job should add a
dbt source freshness
step to the job. The difference between manually adding a step withdbt source freshness
in the job steps or using this flag is that with this flag, a failed freshness will still allow the following steps to run. - run_
lint bool - Whether the CI job should lint SQL changes. Defaults to
false
. - schedule_
cron str - Custom cron expression for schedule
- schedule_
days Sequence[int] - List of days of week as numbers (0 = Sunday, 7 = Saturday) to execute the job at if running on a schedule
- schedule_
hours Sequence[int] - List of hours to execute the job at if running on a schedule
- schedule_
interval int - Number of hours between job executions if running on a schedule
- schedule_
type str - Type of schedule to use, one of everyday/ daysofweek/ customcron/ interval_cron
- self_
deferring bool - Whether this job defers on a previous run of itself
- target_
name str - Target name for the dbt profile
- timeout_
seconds int - [Deprectated - Moved to execution.timeout_seconds] Number of seconds to allow the job to run before timing out
- triggers
Job
Triggers Args - Flags for which types of triggers to use, the values are
github_webhook
,git_provider_webhook
,schedule
andon_merge
. All flags should be listed and set withtrue
orfalse
. Whenon_merge
istrue
, all the other values must be false.\n\ncustom_branch_only
used to be allowed but has been deprecated from the API. The jobs will use the custom branch of the environment. Please remove thecustom_branch_only
from your config. \n\nTo create a job in a 'deactivated' state, set all tofalse
. - triggers_
on_ booldraft_ pr - Whether the CI job should be automatically triggered on draft PRs
- compare
Changes StringFlags - The model selector for checking changes in the compare changes Advanced CI feature
- dbt
Version String - Version number of dbt to use in this job, usually in the format 1.2.0-latest rather than core versions
- deferring
Environment NumberId - Environment identifier that this job defers to (new deferring approach)
- deferring
Job NumberId - Job identifier that this job defers to (legacy deferring approach)
- description String
- Description for the job
- environment
Id Number - Environment ID to create the job in
- errors
On BooleanLint Failure - Whether the CI job should fail when a lint error is found. Only used when
run_lint
is set totrue
. Defaults totrue
. - execute
Steps List<String> - List of commands to execute for the job
- generate
Docs Boolean - Flag for whether the job should generate documentation
- is
Active Boolean - Should always be set to true as setting it to false is the same as creating a job in a deleted state. To create/keep a job in a 'deactivated' state, check the
triggers
config. - job
Completion List<Property Map>Trigger Conditions - Which other job should trigger this job when it finishes, and on which conditions (sometimes referred as 'job chaining').
- job
Id Number - Job identifier
- job
Type String - Can be used to enforce the job type betwen
ci
,merge
andscheduled
. Without this value the job type is inferred from the triggers configured - name String
- Job name
- num
Threads Number - Number of threads to use in the job
- project
Id Number - Project ID to create the job in
- run
Compare BooleanChanges - Whether the CI job should compare data changes introduced by the code changes. Requires
deferring_environment_id
to be set. (Advanced CI needs to be activated in the dbt Cloud Account Settings first as well) - run
Generate BooleanSources - Flag for whether the job should add a
dbt source freshness
step to the job. The difference between manually adding a step withdbt source freshness
in the job steps or using this flag is that with this flag, a failed freshness will still allow the following steps to run. - run
Lint Boolean - Whether the CI job should lint SQL changes. Defaults to
false
. - schedule
Cron String - Custom cron expression for schedule
- schedule
Days List<Number> - List of days of week as numbers (0 = Sunday, 7 = Saturday) to execute the job at if running on a schedule
- schedule
Hours List<Number> - List of hours to execute the job at if running on a schedule
- schedule
Interval Number - Number of hours between job executions if running on a schedule
- schedule
Type String - Type of schedule to use, one of everyday/ daysofweek/ customcron/ interval_cron
- self
Deferring Boolean - Whether this job defers on a previous run of itself
- target
Name String - Target name for the dbt profile
- timeout
Seconds Number - [Deprectated - Moved to execution.timeout_seconds] Number of seconds to allow the job to run before timing out
- triggers Property Map
- Flags for which types of triggers to use, the values are
github_webhook
,git_provider_webhook
,schedule
andon_merge
. All flags should be listed and set withtrue
orfalse
. Whenon_merge
istrue
, all the other values must be false.\n\ncustom_branch_only
used to be allowed but has been deprecated from the API. The jobs will use the custom branch of the environment. Please remove thecustom_branch_only
from your config. \n\nTo create a job in a 'deactivated' state, set all tofalse
. - triggers
On BooleanDraft Pr - Whether the CI job should be automatically triggered on draft PRs
Supporting Types
JobJobCompletionTriggerCondition, JobJobCompletionTriggerConditionArgs
- job_
id int - The ID of the job that would trigger this job after completion.
- project_
id int - The ID of the project where the trigger job is running in.
- statuses Sequence[str]
- List of statuses to trigger the job on. Possible values are
success
,error
andcanceled
.
JobTriggers, JobTriggersArgs
- Git
Provider boolWebhook - Whether the job runs automatically on PR creation
- Github
Webhook bool - Whether the job runs automatically on PR creation
- On
Merge bool - Whether the job runs automatically once a PR is merged
- Schedule bool
- Whether the job runs on a schedule
- Git
Provider boolWebhook - Whether the job runs automatically on PR creation
- Github
Webhook bool - Whether the job runs automatically on PR creation
- On
Merge bool - Whether the job runs automatically once a PR is merged
- Schedule bool
- Whether the job runs on a schedule
- git
Provider BooleanWebhook - Whether the job runs automatically on PR creation
- github
Webhook Boolean - Whether the job runs automatically on PR creation
- on
Merge Boolean - Whether the job runs automatically once a PR is merged
- schedule Boolean
- Whether the job runs on a schedule
- git
Provider booleanWebhook - Whether the job runs automatically on PR creation
- github
Webhook boolean - Whether the job runs automatically on PR creation
- on
Merge boolean - Whether the job runs automatically once a PR is merged
- schedule boolean
- Whether the job runs on a schedule
- git_
provider_ boolwebhook - Whether the job runs automatically on PR creation
- github_
webhook bool - Whether the job runs automatically on PR creation
- on_
merge bool - Whether the job runs automatically once a PR is merged
- schedule bool
- Whether the job runs on a schedule
- git
Provider BooleanWebhook - Whether the job runs automatically on PR creation
- github
Webhook Boolean - Whether the job runs automatically on PR creation
- on
Merge Boolean - Whether the job runs automatically once a PR is merged
- schedule Boolean
- Whether the job runs on a schedule
Package Details
- Repository
- dbtcloud pulumi/pulumi-dbtcloud
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
dbtcloud
Terraform Provider.