This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update all non-major dependencies (actions/checkout, actions/setup-go, alpine, codecov/codecov-action, github.com/gin-gonic/gin, github.com/go-git/go-git/v5, github.com/go-vela/sdk-go, github.com/go-vela/server, github.com/go-vela/types, github.com/go-vela/worker, github.com/urfave/cli/v2, github/codeql-action, skx/github-action-publish-binaries)
• fix(deps): update module gopkg.in/yaml.v2 to v3

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

Related to Allow terminating a running build #56

Give users an ability to cancel their builds via the CLI

Description

What is your idea?

Value

Why is this important? Who does it impact? Will this make something better, faster, etc?

Definition of Done

What is the end goal of this story?

Effort (Optional)

Estimated effort to complete this story? (Best Guess e.g. 1-2 days)

Impacted Personas (Optional)

Which personas will benefit from completing this story? (Users, Administrators, etc)

Description

What is your idea?

The CLI needs the ability to view service logs from a pipeline.

Value

Why is this important? Who does it impact? Will this make something better, faster, etc?

Allows users using services to check their logs via CLI

Definition of Done

What is the end goal of this story?

Logs are viewable

Description

Implement hooks management via the Vela CLI

Value

Offer the same functionality presented in the UI at /org/repo/hooks but via the CLI.
eg.
vela get hooks --org octocat --repo hello-world
vela view hook --org octocat --repo hello-world --hook-number 10

Definition of Done

A user can view hooks through the CLI

Effort (Optional)

2 days

Impacted Personas (Optional)

Users

Description

What is your idea?

Related stories:

go-vela/server#89
go-vela/sdk-go#32

Value

Why is this important? Who does it impact? Will this make something better, faster, etc?

Definition of Done

What is the end goal of this story?

Effort (Optional)

Estimated effort to complete this story? (Best Guess e.g. 1-2 days)

Impacted Personas (Optional)

Which personas will benefit from completing this story? (Users, Administrators, etc)

Description

What is your idea?

Value

Why is this important? Who does it impact? Will this make something better, faster, etc?

Definition of Done

What is the end goal of this story?

Effort (Optional)

Estimated effort to complete this story? (Best Guess e.g. 1-2 days)

Impacted Personas (Optional)

Which personas will benefit from completing this story? (Users, Administrators, etc)

Description

Implement repo favorites management via the Vela CLI

Value

Offer the same functionality presented in the UI at / (home page) but via the CLI.
eg.
vela get favorites or update functionality for vela get repos
vela add favorite --org octocat --repo hello-world

Definition of Done

A user can manage favorites through the CLI

Effort (Optional)

2 days

Impacted Personas (Optional)

Users

Description

What is your idea?

After we upgrade to cli/urfave v2, we should investigate auto-completion again to make the CLI easier to use.

auto-completion docs in v2 library:
https://github.com/urfave/cli/blob/master/docs/v2/manual.md#bash-completion

Value

Why is this important? Who does it impact? Will this make something better, faster, etc?

improves usability

Definition of Done

What is the end goal of this story?

We have options for deciding if we want to move forward with auto-completion.

Right now the CLI requires the value of a secret to be in the command being ran, e.g.

$ vela add secret --type org --org github --repo '*' --name docker_password --value "password"

This means that the secret value might end up in a history file somewhere. It would be cool if vela had a separate prompt for the value of a secret.

$ vela add secret --type org --org github --repo '*' --name docker_password
enter secret value: 

A verification of the secret could be added by prompting twice, similar to how gopass insert works.

vela already does this when doing the initial login:

Trying out vela, excited for this. Thanks! In the spirit of giving constructive feedback, I wanted to open this. There is a confusing message displayed upon initial creation of a config file

To reproduce

I used https://go-vela.github.io/docs/usage/reference/cli/authentication/#configuration-file to first generate my token.

I then used the following command to generate the config file (token and url redacted):

Actual Result

vela generate config --addr <<URL_REDACTED>> --token <<TOKEN_REDACTED>>
time="2019-11-15T10:36:04-06:00" level=warning msg="Unable to find config file @ C:\\Users\\<<USER_REDACTED>>/.vela/config.yml"

The msg text made me concerned this command failed. But inspecting the path mentioned revealed the file was created successfully.

Expected Result

The command succeeds without a message, or with explicit success messaging

Wild Speculation

Perhaps this msg comes earlier in the process, during some initialization step for all vela commands that looks for this config file? In this case, it's a bit of a one-time 🐔 and 🥚 problem

Description

What is your idea?

Update our urfave/cli library to the v2 functionality.

https://github.com/urfave/cli#using-v2-releases

Value

Why is this important? Who does it impact? Will this make something better, faster, etc?

• Reduce technical debt

Definition of Done

What is the end goal of this story?

This repo is using the v2 branch of the urfave/cli library.

Effort (Optional)

Estimated effort to complete this story? (Best Guess e.g. 1-2 days)

N/A