Skip to content

fix: move tasks to separate package#19

Merged
Malaydewangan09 merged 1 commit intomainfrom
fix/package
Dec 30, 2025
Merged

fix: move tasks to separate package#19
Malaydewangan09 merged 1 commit intomainfrom
fix/package

Conversation

@Malaydewangan09
Copy link
Member

What changes are being made and why?


How the changes have been QAed?


Setup Instructions


Contributor Checklist ✅

  • PR Title and commits follows conventional commits
  • Add a closes #ISSUE_ID or fixes #ISSUE_ID in the description if the PR relates to an opened issue.
  • Documentation updated (plugin docs from @Schema for properties and outputs, @Plugin with examples, README.md file with basic knowledge and specifics).
  • Setup instructions included if needed (API keys, accounts, etc.).
  • Prefix all rendered properties by r not rendered (eg: rHost).
  • Use runContext.logger() to log enough important infos where it's needed and with the best level (DEBUG, INFO, WARN or ERROR).

⚙️ Properties

  • Properties are declared with Property<T> carrier type, do not use @PluginProperty.
  • Mandatory properties must be annotated with @NotNull and checked during the rendering.
  • You can model a JSON thanks to a simple Property<Map<String, Object>>.

🌐 HTTP

  • Must use Kestra’s internal HTTP client from io.kestra.core.http.client

📦 JSON

  • If you are serializing response from an external API, you may have to add a @JsonIgnoreProperties(ignoreUnknown = true) at the mapped class level. So that we will avoid to crash the plugin if the provider add a new field suddenly.
  • Must use Jackson mappers provided by core (io.kestra.core.serializers)

New plugins / subplugins

  • Make sure your new plugin is configured like mentioned here.
  • Add a package-info.java under each sub package respecting this format and choosing the right category.
  • Every time you use runContext.metric(...) you have to add a @Metric (see this doc)
  • Docs don't support to have both tasks/triggers in the root package (e.g. io.kestra.plugin.kubernetes) and in a sub package (e.g. io.kestra.plugin.kubernetes.kubectl), whether it's: all tasks/triggers in the root package OR only tasks/triggers in sub packages.
  • Icons added in src/main/resources/icons in SVG format and not in thumbnail (keep it big):
    • plugin-icon.svg
    • One icon per package, e.g. io.kestra.plugin.aws.svg
    • For subpackages, e.g. io.kestra.plugin.aws.s3, add io.kestra.plugin.aws.s3.svg
      See example here.
  • Use "{{ secret('YOUR_SECRET') }}" in the examples for sensible infos such as an API KEY.
  • If you are fetching data (one, many or too many), you must add a Property<FetchType> fetchType to be able to use FETCH_ONE, FETCH and even STORE to store big amount of data in the internal storage.
  • Align the """ to close examples blocks with the flow id.
  • Update the existing index.yaml for the main plugin, and for each new subpackage add a metadata file named exactly after the subpackage (e.g. s3.yaml for io.kestra.plugin.aws.s3) under src/main/resources/metadata/, following the same schema.

🧪 Tests

  • Unit Tests added or updated to cover the change (using the RunContext to actually run tasks).
  • Add sanity checks if possible with a YAML flow inside src/test/resources/flows.
  • Avoid disabling tests for CI. Instead, configure a local environment whenever it's possible with .github/setup-unit.sh (to be set executable with chmod +x setup-unit.sh) (which can be executed locally and in the CI) all along with a new docker-compose-ci.yml file (do not edit the existing docker-compose.yml). If needed, create an executable (chmod +x cleanup-unit.sh) cleanup-unit.sh to remove the potential costly resources (tables, datasets, etc).
  • Provide screenshots from your QA / tests locally in the PR description. The goal here is to use the JAR of the plugin and directly test it locally in Kestra UI to ensure it integrates well.

📤 Outputs

  • Do not send back as outputs the same infos you already have in your properties.
  • If you do not have any output use VoidOutput.
  • Do not output twice the same infos (eg: a status code, an error code saying the same thing...).

@github-project-automation github-project-automation bot moved this to To review in Pull Requests Dec 30, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 30, 2025

📦 Artifacts

Name Size Updated Expiration
jar 29.04 KB Dec 30, 25, 6:33:05 AM UTC Jan 6, 26, 6:33:05 AM UTC

🧪 Java Unit Tests

TestsPassed ✅SkippedFailedTime ⏱
Java Tests Report15 ran15 ✅0 ⚠️0 ❌2s 669ms

🔁 Unreleased Commits

8 commits since v1.1.0

SHA Title Author Date
6a7f9f2 chore: update contributor guidelines in PR template Malay Dewangan Nov 7, 25, 9:22:05 AM UTC
ff8ae0b ci: sync release.yml from plugin-template François Delbrayelle Nov 12, 25, 1:54:54 PM UTC
2e31d72 build(deps): bump org.aspectj:aspectjweaver from 1.9.24 to 1.9.25 dependabot[bot] Nov 10, 25, 3:28:34 AM UTC
5248e82 chore: update contributor guidelines in PR template Malay Dewangan Nov 27, 25, 8:07:07 AM UTC
9895f69 chore(metadata): add plugin metadata Malay Dewangan Nov 27, 25, 6:36:45 PM UTC
ae9f81e docs(gitlab-metadata): add metadata AJ Emerich Dec 4, 25, 3:59:26 PM UTC
ba2f003 build(deps): bump org.aspectj:aspectjweaver from 1.9.25 to 1.9.25.1 dependabot[bot] Dec 22, 25, 3:19:06 AM UTC
c2e5d5b build(deps): bump com.gradleup.shadow from 9.2.2 to 9.3.0 dependabot[bot] Dec 8, 25, 3:20:56 AM UTC

@Malaydewangan09 Malaydewangan09 merged commit a86ccb4 into main Dec 30, 2025
3 checks passed
@Malaydewangan09 Malaydewangan09 deleted the fix/package branch December 30, 2025 06:35
@github-project-automation github-project-automation bot moved this from To review to Done in Pull Requests Dec 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Add a core package to avoid hiding tasks in the docs

1 participant