kubesphere / kubesphere/ks-devops

Credentials password is null

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

Nobody has claimed this yet.

kind/bug
Dominant language
Go
Stars
164
Forks
140
PR merge metrics
No merged PRs in 30d

Description

What is version of KubeSphere DevOps has the issue?

dev-v3.3.0-alpha.1-d92409f

How did you install the Kubernetes? Or what is the Kubernetes distribution?

./kk create cluster --with-kubernetes v1.21.5 --with-kubesphere v3.2.1

What happened?

When creating a github (Code Repository) pipeline, the returned certificate password is an empty string, and the project list cannot be obtained correctly.

Relevant log output

No response

Additional information
When the return value of the API("kapis/devops.kubesphere.io/v1alpha3/devops/testv8rd7/credentials/password-null?content=1") ) is like this
{
 ....
 "data": {
  "id": "xx",
  "password": "xx",
  "username": "xxx"
 },
 "type": "credential.devops.kubesphere.io/basic-auth"
}
will get the desired result, but when password is set to empty, no information will be obtained.
{
 ....
 "data": {
  "id": "xx",
  "password": "",
  "username": "xxx"
 },
 "type": "credential.devops.kubesphere.io/basic-auth"
}

image

Contributor guide

Open the contributing guide

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.

Research direction

Start by reproducing the GitHub Code Repository pipeline case against the kapis/devops.kubesphere.io/v1alpha3/devops/testv8rd7/credentials/password-null?content=1 endpoint. Compare behavior when the credential password is populated versus an empty string, and confirm that the empty-password response still allows the project list to be obtained.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
api, authentication, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.