Skip to content
This repository has been archived by the owner on Sep 15, 2022. It is now read-only.

Investigate if we can get rid of the addons version #60

Closed
mszostok opened this issue Dec 4, 2019 · 5 comments
Closed

Investigate if we can get rid of the addons version #60

mszostok opened this issue Dec 4, 2019 · 5 comments
Labels
area/service-management Issues or PRs related to service management

Comments

@mszostok
Copy link
Contributor

mszostok commented Dec 4, 2019

Description

Currently, we have 3 layers for versioning:

  1. repository version which contains sets of addons
  2. addons version <- problematic part
  3. Helm Chart version which is wrapped a given addon

From the beginning, an addon was considered as an abstraction layer over a Helm chart which provides all information required to convert the chart into a Service Class. We added the bundle versions which are a new layer and directly not supported in Service Catalog.

The most problematic part is that the version of the addon is not used anywhere from the beginning and it's confusing for our users who need to create and maintain the addons repository.

We need to have a clear vision if we need the bundle version at all. If we cannot find any purpose for this versioning then we should deprecate that and remove it in the next version.

AC:

  • a clear statement for the future of the addons versioning (if we can deprecate that and remove it in the next version)
@mszostok mszostok added the area/service-management Issues or PRs related to service management label Dec 4, 2019
@mszostok mszostok added this to the Backlog_Gopher milestone Dec 4, 2019
@mszostok mszostok changed the title Investigation if we can get rid of the addons version Investigate if we can get rid of the addons version Dec 4, 2019
@polskikiel
Copy link
Contributor

Consider if we need versioning for this issue: #61

@stale
Copy link

stale bot commented Mar 3, 2020

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Mar 3, 2020
@mszostok mszostok removed the stale label Mar 3, 2020
@stale
Copy link

stale bot commented May 2, 2020

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label May 2, 2020
@stale
Copy link

stale bot commented May 9, 2020

This issue has been automatically closed due to the lack of recent activity.

@stale stale bot closed this as completed May 9, 2020
@PK85 PK85 reopened this May 15, 2020
@stale stale bot removed the stale label May 15, 2020
@pbochynski pbochynski removed this from the Backlog_Gopher milestone May 27, 2020
@PK85
Copy link
Collaborator

PK85 commented Jun 4, 2020

Three times stale, closing it. @mszostok please reopen if you want to keep it, but make sure to un-stale that every month.

@PK85 PK85 closed this as completed Jun 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/service-management Issues or PRs related to service management
Projects
None yet
Development

No branches or pull requests

4 participants