Skip to content

Bug: devspace set encryptionkey logs the key instead of the cluster name on success #1

Open

Description

@SamYu

What happened?
When attempting to set encryptionkey for devspace cloud via devspace set encryptionkey <KEY> --cluster=<CLUSTER>, the success message outputs Succesfully set encryption key for cluster <KEY> with the key in the success message instead of the cluster name.

This is the command and output

devspace set encryptionkey "SOME_KEY" --cluster=CLUSTER_NAME
[info]   Successfully set encryption key for cluster SOME_KEY

What did you expect to happen instead?
The success message should say the cluster name.

How can we reproduce the bug? (as minimally and precisely as possible)

  1. devspace set encryptionkey <KEY> --cluster=<CLUSTER>

Local Environment:

  • DevSpace Version: 5.0.2
  • Also using devspace-cloud plugin
  • Operating System: mac
  • Deployment method: kubectl apply

Kubernetes Cluster:

  • Cloud Provider: google
  • Kubernetes Version: 1.16.6-beta0

Anything else we need to know?

/kind bug

Activity

  1. FabianKramm commented on Aug 19, 2020

    @FabianKramm
    Contributor

    @SamYu thanks for reporting this issue! You are correct, should be an easy fix

  2. self-assigned this
    on Aug 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions