Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using Bitbucket personal access token as k8s secret during factory resolution #18386

Closed
skabashnyuk opened this issue Nov 17, 2020 · 0 comments
Closed
Assignees
Labels
area/factory/server Server side of factory implementation kind/task Internal things, technical debt, and to-do tasks to be performed. status/in-progress This issue has been taken by an engineer and is under active development.
Milestone

Comments

@skabashnyuk
Copy link
Contributor

Is your task related to a problem? Please describe.

We want to be able to access devfile content that is stored in the Bitbucket server.

Describe the solution you'd like

Implement ability to use
k8s secret with bitbucket personal access token
during the factory resolution process.

apiVersion: v1
kind: Secret
metadata:
  name: bitbucket-personal-access-token-secret
  labels:
    app.kubernetes.io/part-of: che.eclipse.org
    app.kubernetes.io/component: bitbucket-personal-access-token
  annotations:
    che.eclipse.org/expired-after: 12323423
    che.eclipse.org/che-userid: 7234090-45345234
    che.eclipse.org/bitbucket-userid: 34593094509
    che.eclipse.org/bitbucket-username: 'tshevchenko'
data:
  token: ZHNhZmFkZmFzZGZxMzRyMzRyMTM0

Nodes :

  • secrets with missed or expired date should not be taken into account.

Describe alternatives you've considered

n/a

Additional context

#18226 (comment)

@skabashnyuk skabashnyuk added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Nov 17, 2020
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Nov 17, 2020
@skabashnyuk skabashnyuk added area/che-server area/factory/server Server side of factory implementation and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. area/che-server labels Nov 17, 2020
@mshaposhnik mshaposhnik self-assigned this Dec 9, 2020
@mshaposhnik mshaposhnik added the status/in-progress This issue has been taken by an engineer and is under active development. label Dec 9, 2020
@skabashnyuk skabashnyuk added this to the 7.24 milestone Dec 9, 2020
@skabashnyuk skabashnyuk modified the milestones: 7.24, 7.25 Dec 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/factory/server Server side of factory implementation kind/task Internal things, technical debt, and to-do tasks to be performed. status/in-progress This issue has been taken by an engineer and is under active development.
Projects
None yet
Development

No branches or pull requests

3 participants