Skip to content

Feature Request: Support for Configurable Default Options in Cirrus Commands #1

Description

@grasmarcussanti129

Summary

Currently, Cirrus CLI requires users to specify options for each command, which can become repetitive, especially for commonly used commands. A feature that allows users to set global or per-command default options in the cirrus.toml configuration file would enhance user experience and streamline command execution.

Description

When working with Salesforce scratch orgs and other commands, users often use similar parameters. For example, the --name and --alias options for create_scratch are often the same for multiple commands. Having to re-specify these every time is tedious and can lead to errors.

Proposed Solution

  • Introduce a [defaults] section in the cirrus.toml file where users can define default options for specified commands.
  • For example:
    [defaults]
    create_scratch.name = "default"
    create_scratch.alias = "my-scratch-org"
  • If these defaults are defined, they should automatically apply unless overridden by the command line options.

Benefits

  • Reduces repetitive typing and streamlines user workflow.
  • Minimizes potential errors from manual input of command options.

This feature could greatly improve the usability of Cirrus, particularly for users who frequently execute similar commands in their Salesforce development workflow.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions