Skip to content

Check blocks all *, not just "*" #213

@Loki-101

Description

@Loki-101

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?

  • I have searched the existing issues before opening this issue.
  • I have provided all relevant details and tested my reproduction steps.
  • I have checked to my best capabilities and believe this is a bug with the software, and not a configuration issue with my specific system.
  • I have made sure to check that this bug is the fault of Blueprint and is not caused by stock Pterodactyl.

Metadata

Metadata

Assignees

Labels

scope:cliIssues or pull requests related to the Blueprint CLI.

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions