Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(cli): configure in non-interactive mode #158

Merged
merged 3 commits into from
Jul 6, 2020

Commits on Jul 4, 2020

  1. feat(cli): configure in non-interactive mode

    >As a Lacework CLI user that uses the tool in CI/CD Pipelines,
    >I want to have a non-interactive way to configure the Lacework CLI,
    >So I don't have to manually create the config file `~/.lacework.toml` inside my pipeline.
    
    When a user runs:
    ```
    $ lacework configure -a foo -k bar -s bubu --noninteractive
    ```
    The result is the creation of the `~/.lacework.toml` without asking the user
    to validate the inputs. (non-interactive mode)
    
    The command loads these settings from all sources, as usual, environment
    variables, parameters (including `--json_file`), and the actual config file.
    
    Closes #112
    
    Signed-off-by: Salim Afiune Maya <[email protected]>
    afiune committed Jul 4, 2020
    Configuration menu
    Copy the full SHA
    be89309 View commit details
    Browse the repository at this point in the history

Commits on Jul 6, 2020

  1. test(cli): configure --noninteractive mode

    Signed-off-by: Salim Afiune Maya <[email protected]>
    afiune committed Jul 6, 2020
    Configuration menu
    Copy the full SHA
    77dc9c0 View commit details
    Browse the repository at this point in the history
  2. docs(cli): update global --noninteractive flag

    Signed-off-by: Salim Afiune Maya <[email protected]>
    afiune committed Jul 6, 2020
    Configuration menu
    Copy the full SHA
    8333781 View commit details
    Browse the repository at this point in the history