docs: state connection properties per task instead of plugin defaults - #180
Merged
Conversation
pluginDefaults was removed in the latest Kestra release, so the docs must no longer point users at it or at kestra.io/docs/workflow-components/plugin-defaults. Connection properties are now stated on each task.
Contributor
📦 Artifacts
🧪 Java Unit Tests
🔁 Unreleased Commits6 commits since
|
Contributor
Tests report quick summary:success ✅ > tests: 3, success: 3, skipped: 0, failed: 0 unfold for details
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removes references to
pluginDefaults, which was removed in the latest Kestrarelease, from this plugin's documentation. Connection properties are now stated
on each task.
Part of a sweep across the plugin repositories: the docs link to
kestra.io/docs/workflow-components/plugin-defaultsand the surrounding prosewould otherwise point users at a removed feature and a dead docs page.