Failed to delete secret (due to special charecters)

Open
#561 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
cli

Research direction

Start by reproducing the failed deletion from the Influx GUI and the Influx CLI using the reported Secret ID containing special characters. Trace the secret deletion entry point and compare how the identifier is accepted during creation versus deletion. Done means the affected secret can be deleted reliably, with a regression test covering this identifier.

Written by the indexing model from the issue text.

Description

For starters this is not a big issue.

In the GUI I added a new secret key but, by accident, I pasted the secret value also into the secret key.
This was accepted by the system however obvious not wanted, I tried to correct this mistake to delete this secret key again but this is not possible "Failed to delete secret"

I also observed that there is an option available to copy this to the clipboard "the Secret ID ' xK^mVYxm!39^v7wjN7%^rH' has been copied to clipboard." Two remarks about this:

  • Nothing is really happening but perhaps I should read the manual in this respect better (and in a way this is good)
  • The name of Secret key is imho now called more correctly Secret ID (which most likely would not have prevented my mistake)

Tested inside the GUI of InfluxDB version 2.6.1. and after a new pull
In both version the this key/id (' xK^mVYxm!39^v7wjN7%^rH') was accepted but could be deleted.

  • Influx CLI 2.6.1 (git: 61c5b4d) build_date: 2022-12-29T15:41:09Z
  • Influx CLI dev (git: a79a2a1b825867421d320428538f76a4c90aa34c) build_date: 2024-04-16T14:34:32Z

Possible reasons is the use of special characters but why was it accepted in the first place?
Question: is the an alternative way to delete this key?

Dominant language
Go
Stars
75
Forks
22
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from influxdata/influx-cli

All issues in influxdata/influx-cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.