Windmill integration

[adelowo]

• Create jobs in windmill. These are regular code/scripts that will be wrapped into Windmill compatible layer
• Created a tiny windmill client/sdk
• create scheduled job in windmill when a control is added to a job
• add support for both on success and failure scripts which would be appended to scheduled jobs - globally applied

entConfig:

  windmill:
    enabled: true
    baseURL: "http://localhost"
    workspace: "test"
    token: "xyz"
    defaultTimeout: "30s"
    onFailureScript: "u/admin/glimmering_script"
    onSuccessScript: "u/admin/glimmering_script"

mutation($input: CreateScheduledJobInput!) {
  createScheduledJob(input: $input) {
    scheduledJob {
      id
    }
  }
}

{
  "input": {
    "cron": "0 22 * * 1-5",
    "downloadURL": "https://gist.githubusercontent.com/",
    "title": "SSL scanning test",
  },
}

[golanglemonade]

I think this should happen after the next.Mutate, so we can make sure the validation happens correctly and then the flow is created in windmill

Suggested change

	if mutation.Op() == ent.OpCreate {
	if err := createWindmillFlow(ctx, mutation); err != nil {
	return nil, fmt.Errorf("failed to create windmill flow: %w", err)
	}
	}
	return next.Mutate(ctx, mutation)
	retVal, err := next.Mutate(ctx, mutation)
	if err != nil {
	return err
	}
	if mutation.Op() == ent.OpCreate {
	if err := createWindmillFlow(ctx, mutation); err != nil {
	return nil, fmt.Errorf("failed to create windmill flow: %w", err)
	}
	}
	return retVal, err

[golanglemonade]

How does this work if a user updates the job?

[adelowo]

for this, I do not want to make fields like the windmill path optional - as they aren't. the job creation also does all possible validation asides the context.

let me know if to move still

[golanglemonade]

gotcha, that makes sense - but we would still need to be able to roll this back if the transaction fails so we don't end up with a hanging flow if something causes the db transaction to fail

[theopenlane-bender]

🔧 Configuration Changes Detected

This PR contains changes that will affect the Helm chart configuration. A draft infrastructure PR has been automatically created to preview these changes:

📋 Draft PR: theopenlane/openlane-infra#100

Changes Preview:

- 🔄 Merged Helm values.yaml
- 🆕 Created External Secrets templates
- ✨ Created ConfigMap template

The infrastructure PR will automatically convert from draft to ready for review once this core PR is merged.

[theopenlane-bender]

🔧 Configuration Changes Detected

This PR contains changes that will affect the Helm chart configuration. A draft infrastructure PR has been automatically created to preview these changes:

📋 Draft PR: theopenlane/openlane-infra#100

Changes Preview:

🔧 Applying Helm configuration changes...

- 🔄 Merged Helm values.yaml🔄 Merging Helm values.yaml
🔀 Merging with existing chart values...
📋 Replacing core section...
🔐 Merging external secrets configuration...
📊 Analyzing changes...

• External secrets configuration updated

The infrastructure PR will automatically convert from draft to ready for review once this core PR is merged.

[theopenlane-bender]

🔧 Configuration Changes Detected

This PR contains changes that will affect the Helm chart configuration. A draft infrastructure PR has been automatically created to preview these changes:

📋 Draft PR: theopenlane/openlane-infra#111

Changes Preview:

🔧 Applying Helm configuration changes...
Updating ConfigMap template
✅ Updated ConfigMap template

- ✅ Updated ConfigMap template

The infrastructure PR will automatically convert from draft to ready for review once this core PR is merged.

[sonarqubecloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 20%)
5.6% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud