Current Behavior
The new check blocking "*" catches any argument with * in it, including blueprint -i *.blueprint, resulting in FATAL: "*" cannot be used as an argument. when performing a standard update.
Expected Behavior
Only "*" passed as an argument should be blocked by this check, as intended.
Steps to Reproduce
Tested in the Docker environment https://github.com/BlueprintFramework/docker/ with the recommended alias expanding blueprint into docker compose -f /srv/pterodactyl/docker-compose.yml exec panel blueprint
blueprint -upgrade remote blueprintframework/framework remote-metadata
blueprint -i *.blueprint
You will then see FATAL: "*" cannot be used as an argument.
Blueprint Version
rolling
Panel Version
1.12.2
Is there an existing issue for this?
Current Behavior
The new check blocking "*" catches any argument with * in it, including
blueprint -i *.blueprint, resulting inFATAL: "*" cannot be used as an argument.when performing a standard update.Expected Behavior
Only
"*"passed as an argument should be blocked by this check, as intended.Steps to Reproduce
Tested in the Docker environment https://github.com/BlueprintFramework/docker/ with the recommended alias expanding
blueprintintodocker compose -f /srv/pterodactyl/docker-compose.yml exec panel blueprintblueprint -upgrade remote blueprintframework/framework remote-metadata blueprint -i *.blueprintYou will then see
FATAL: "*" cannot be used as an argument.Blueprint Version
rolling
Panel Version
1.12.2
Is there an existing issue for this?