Summary

It is possible to access individual parameters, labels, or annotations from within a workflow via

• workflow.parameters.<NAME>,
• workflow.labels.<NAME>,
• and workflow.annotations.<NAME> respectively.

It is also possible to get all parameters as a JSON string:

• workflow.parameters

It would be great if also labels and annotations could be exposed that way:

Summary

Add a link to docs/operator-manual/security.md from root-level security.md.

Motivation

Reduce friction when users are trying to find in-depth security recommendations.

Proposal

Add a new section to the root-level security.md with a brief sentence and link to the operator docs.

Is your feature request related to a problem? Please describe.
Each event received/emitted from event sources already has an event ID attached, so that it can be used in Sensor to achieve uniqueness, this ID is currently generated automatically. For some of the event sources like Kafka, we can extend the feature to generate a unique ID based on the original message, so that even there's a dup

Users can tell Ploomber to track changes to configuration files via resources_, however, to track changes, we compute a file hash which may take too long if the file is large.

We should show a warning if this happens, resources_ should not be used with large files.

Describe the solution you'd like
Unit tests should be added to the files in the executor package