[GH-ISSUE #587] [BUG] asynq cli ignore cluster param in config file #285

Closed
opened 2026-03-02 05:20:11 +03:00 by kerem · 3 comments
Owner

Originally created by @khasanovbi on GitHub (Dec 17, 2022).
Original GitHub issue: https://github.com/hibiken/asynq/issues/587

Originally assigned to: @hibiken on GitHub.

Originally created by @khasanovbi on GitHub (Dec 17, 2022). Original GitHub issue: https://github.com/hibiken/asynq/issues/587 Originally assigned to: @hibiken on GitHub.
kerem 2026-03-02 05:20:11 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@hibiken commented on GitHub (Dec 18, 2022):

It should be bound by these two lines: github.com/hibiken/asynq@c08f142b56/tools/asynq/cmd/root.go (L320-L321)

Would you mind verifying this bug?

<!-- gh-comment-id:1356865073 --> @hibiken commented on GitHub (Dec 18, 2022): It should be bound by these two lines: https://github.com/hibiken/asynq/blob/c08f142b5666b5983db9bd84764b7917b953d3a2/tools/asynq/cmd/root.go#L320-L321 Would you mind verifying this bug?
Author
Owner

@khasanovbi commented on GitHub (Dec 18, 2022):

I don't see that viper.GetBool("cluster") used in code, instead of that flag used directly

<!-- gh-comment-id:1356868766 --> @khasanovbi commented on GitHub (Dec 18, 2022): I don't see that `viper.GetBool("cluster")` used in code, instead of that flag used directly
Author
Owner

@hibiken commented on GitHub (Dec 19, 2022):

Ah, you're right. Thanks for filing this issue

<!-- gh-comment-id:1357078187 --> @hibiken commented on GitHub (Dec 19, 2022): Ah, you're right. Thanks for filing this issue
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/asynq#285
No description provided.