You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The last argument is only treated as a deployment name when it starts with component- or module-, so post-deploy-pipeline (and vault-backoffice in components.yaml) is mistaken for another config file. The script then tries to load it as YAML, fails, and deploys everything instead of the one release.
Fix: treat a trailing argument that does not end with .yaml/.yml as the deployment-name filter. PR follows from soroush5:fix/deploy-single-postdeploy-filter.
changed the title [-]deploy.py ignores single-deployment filter for post-deploy and vault releases[/-][+][Deployment] UnknownClient - v0.0.0 - 2026-09-10[/+]on Sep 10, 2026
Activity
[-]deploy.py ignores single-deployment filter for post-deploy and vault releases[/-][+][Deployment] UnknownClient - v0.0.0 - 2026-09-10[/+]