Skip to content
This repository has been archived by the owner on Dec 21, 2023. It is now read-only.

Show secret scope and keys in overview table #6296

Closed
3 tasks
johannes-b opened this issue Dec 7, 2021 · 1 comment · Fixed by #6695
Closed
3 tasks

Show secret scope and keys in overview table #6296

johannes-b opened this issue Dec 7, 2021 · 1 comment · Fixed by #6695
Assignees
Labels
bridge:settings-screen bridge.2.0 Bridge Version 2 good first issue Issues for getting started developing Keptn

Comments

@johannes-b
Copy link
Member

Use case

Current screen:

image

As a user, I would like to see the specified scope of a secret and the keys in the secret after creating a secret:

image

Details:

  • Scope: Single value
  • Keys: List of values
  • The GET /secrets endpoint provides this information
{
  "Secrets": [
    {
      "name": "slack-secret",
      "scope": "keptn-webhook-service",
      "keys": [
        "webhook-identifier"
      ]
    }
  ]
}

Definition of Done:

  • UI test cover the updated table
  • Feature is implemented
  • Screenshots in docs are updated (if needed)
@johannes-b johannes-b added good first issue Issues for getting started developing Keptn bridge.2.0 Bridge Version 2 bridge:settings-screen labels Dec 7, 2021
@johannes-b johannes-b added this to the 0.13.0 (Bridge) milestone Dec 7, 2021
@johannes-b johannes-b changed the title Keptn Bridge: Show secret scope and keys in overview table Show secret scope and keys in overview table Dec 7, 2021
@thisthat thisthat added the ready-for-refinement Issue is relevant for the next backlog refinment label Dec 7, 2021
@thisthat thisthat removed the ready-for-refinement Issue is relevant for the next backlog refinment label Jan 11, 2022
@lucasclerissepro
Copy link

Would be happy to help with that!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bridge:settings-screen bridge.2.0 Bridge Version 2 good first issue Issues for getting started developing Keptn
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants