Add pull policy to run container task

[mrsimonemms]

Please specify parts of this PR update:

• Specification
• Schema
• Examples
• Extensions
• Use Cases
• Community
• CTK
• Other

Discussion or Issue link:

Discussion
Fixes #1138

What this PR does:

Adds a pull policy to the run.container task. This has the values ifNotPresent (default), always and never, with the same functionality as in Kubernetes.

Additional information:

[mrsimonemms]

I've not updated the versions from 1.0.2, but I'm happy to do so - should this be to 1.0.3 or 1.1.0?

[cdavernas]

@mrsimonemms It should be 1.0.3

[cdavernas]

LGTM! Cheers ❤️

[Copilot]

Pull request overview

This PR adds support for configuring container image pull policies in the run.container task, aligning with Kubernetes conventions. The pull policy controls when container images should be fetched from the registry.

• Adds a pullPolicy field to the container task schema with three possible values: ifNotPresent (default), always, and never
• Updates documentation to describe the new field
• Provides an example workflow demonstrating the pull policy usage

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
schema/workflow.yaml	Adds the pullPolicy field definition with enum values to the container task schema
examples/run-container-with-pull-policy.yaml	Provides a new example workflow demonstrating the pullPolicy: always configuration
dsl-reference.md	Documents the new pullPolicy field in the container task reference section

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[mrsimonemms]

@cdavernas would you like me to update every 1.0.2 to 1.0.3, or is there an automation that does that?

[cdavernas]

@cdavernas would you like me to update every 1.0.2 to 1.0.3, or is there an automation that does that?

No automation as of now, it's a replace all kind of fix.

[mrsimonemms]

@cdavernas ok, I'll do as an extra commit tomorrow