fix(install): keep wasm plugins on primary registry - #1084
Open
zcxGGmu wants to merge 1 commit into
Open
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
2 participants
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
AGENTTEAMS_HIGRESS_WASM_PLUGIN_REGISTRYdefaulting to the primarycn-hangzhouregistry for Higress WASM plugin pulls.Fixes #429
Testing
bash tests/check-installer-wasm-registry.shbash tests/check-installer-pre-1.2-env-compat.shbash tests/check-agentteams-rename-defaults.shbash -n install/agentteams-install.sh tests/check-installer-wasm-registry.shpython - <<'PY' ... yaml.safe_load(.github/workflows/helm-lint.yml) ... PYgit diff --checkNotes
pwshis not installed in this environment; the new CI check verifies the expected PowerShell env-file contract textually.