Dander 0.4.0rc1: manifest-scoped connector plugins - #58
Merged
Conversation
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
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.
Summary
dander.yamland activate only declareddander.connectorsentry pointsdander plugins installplus source-free Dockerfile installation0.4.0rc1Compatibility
Existing manifests without
pluginsremain unchanged. Explicit plugins may replace a matching built-in engine; two plugins claiming the same engine fail clearly. Authentication remains in Dander core, and Salesforce has not moved yet.Checks
uv run ruff check .uv run ruff format --check .uv run mypy src testsuv run pytest— 690 passedNo tag, PyPI publication, Terraform apply, GCP mutation, Salesforce repository creation, deployment, or schedule change occurred.