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.

Sign up for GitHub

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

Jump to bottom

Document how Developers private configurations should be managed (not in a Devfile) #1033

Closed
l0rd opened this issue Feb 15, 2023 · 1 comment
Closed

Document how Developers private configurations should be managed (not in a Devfile) #1033

l0rd opened this issue Feb 15, 2023 · 1 comment
Labels
area/documentation Improvements or additions to documentation lifecycle/rotten Rotten items. These items have been stale for 60 days and are now closed. lifecycle/stale Stale items. These items have not been updated for 90 days. sprint/current

Comments

@l0rd
Copy link
Contributor

l0rd commented Feb 15, 2023

Which area this feature is related to?

Data such as:

  • Developer git credentials
  • SSH Keys
  • Maven settings.xml
  • Developer dotfiles
  • TLS certificates
  • Proxy settings

are not supposed to be specified in a Devfile shared with the rest of the team. So we should

  1. discourage to use the a devfile to store this information
  2. define a conventions to support developers private configurations for tools that implement the Devfile API

Describe the solution you'd like

Add a section of the Devfile documentation about developers private configurations and how Kubernetes secrets and config maps should (or not) be used for that. We should re-use (move) the DevWorkspace operator documentation for that.
@l0rd l0rd added the area/documentation Improvements or additions to documentation label Feb 15, 2023
@l0rd l0rd mentioned this issue Feb 15, 2023
Closed
@l0rd l0rd changed the title Document how Developers private configurations should be managed (that are not supposed to be shared in a Devfile) Document how Developers private configurations should be managed (not in a Devfile) Feb 15, 2023
@l0rd l0rd self-assigned this Feb 18, 2023
@l0rd l0rd mentioned this issue Feb 18, 2023
Closed
@kadel kadel mentioned this issue Feb 20, 2023
Closed
@l0rd l0rd mentioned this issue Mar 6, 2023
Closed
7 tasks
@l0rd l0rd mentioned this issue Mar 22, 2023
Closed
@nichjones1 nichjones1 moved this to 📋 Backlog in Eclipse Che Team B Backlog Mar 24, 2023
@l0rd l0rd removed their assignment Apr 5, 2023
@Jdubrick Jdubrick moved this to Refinement in Devfile Project Feb 27, 2024
@michael-valdron michael-valdron moved this from Refinement to Backlog in Devfile Project Mar 20, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Aug 5, 2024

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.

@github-actions github-actions bot added the lifecycle/stale Stale items. These items have not been updated for 90 days. label Aug 5, 2024
@github-actions github-actions bot added the lifecycle/rotten Rotten items. These items have been stale for 60 days and are now closed. label Oct 5, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 5, 2024
@github-project-automation github-project-automation bot moved this from Backlog to Done ✅ in Devfile Project Oct 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/documentation Improvements or additions to documentation lifecycle/rotten Rotten items. These items have been stale for 60 days and are now closed. lifecycle/stale Stale items. These items have not been updated for 90 days. sprint/current
Projects
Devfile Project
Status: Done ✅
Milestone
No milestone
Development

No branches or pull requests
1 participant
@l0rd