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

Enable consistent Versioning Information #24

Open
7 tasks
In-Ko opened this issue Feb 1, 2021 · 1 comment
Open
7 tasks

Enable consistent Versioning Information #24

In-Ko opened this issue Feb 1, 2021 · 1 comment
Labels
component/landscaper Landscape Installer effort/2w Effort for issue is around 2 weeks kind/task General task lifecycle/rotten Nobody worked on this for 12 months (final aging stage) status/blocked Issue is blocked (e.g. because of dependencies)
Milestone

Comments

@In-Ko
Copy link
Collaborator

In-Ko commented Feb 1, 2021

Description
Endusers need to know exactly which versions of Landscaper CLi / Components CLI and Landscaper itself are used.
This is especially needed at the moment due to the fact that a lot of things are changing in all three components, and endusers facing problems need to report to us / landscaper colleagues which versions they have been using when a certain issue occurred.
So we have to update Landscaper CLI version command to display the versions of a) the Landscaper CLI itself, b) the Component-CLI and c) the Landscaper version (e.g. = Helm Chart Version) deployed when the quickstart command is used.

Done Criteria

  • All Features implemented
  • Code has been reviewed by other team members
  • Unit Tests created for new code
  • Integration Test Suite updated (if applicable)
  • Internal technical Documentation updated
  • Enduser Documentation updated (if applicable)
  • Successful demonstration in Review
@In-Ko In-Ko added kind/task General task size/m Size of pull request is medium (see gardener-robot robot/bots/size.py) component/landscaper-ext labels Feb 1, 2021
@In-Ko In-Ko mentioned this issue Feb 1, 2021
7 tasks
@guewa guewa self-assigned this Feb 3, 2021
@guewa guewa removed their assignment Feb 12, 2021
@In-Ko
Copy link
Collaborator Author

In-Ko commented Feb 15, 2021

Status after Sprint 1b:

  • Currently the go get does not work, due to this the installation documentation has been adjusted (https://github.com/gardener/landscapercli/blob/master/docs/installation.md)
  • A small fix has been provided to get the latest versions into the CLI version command.
  • So as of now, this works, but the real solution is blocked due to the go get issue. We will have to work on this backlog item whenever the go get installation has been fixed.

@In-Ko In-Ko added the status/blocked Issue is blocked (e.g. because of dependencies) label Feb 15, 2021
@In-Ko In-Ko added this to the 2021-Q1 milestone Feb 15, 2021
@gardener-robot gardener-robot added effort/2w Effort for issue is around 2 weeks and removed size/m Size of pull request is medium (see gardener-robot robot/bots/size.py) labels Mar 8, 2021
@In-Ko In-Ko added component/landscaper Landscape Installer and removed component/landscaper-ext labels May 17, 2021
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Nov 14, 2021
@gardener-robot gardener-robot added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels May 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/landscaper Landscape Installer effort/2w Effort for issue is around 2 weeks kind/task General task lifecycle/rotten Nobody worked on this for 12 months (final aging stage) status/blocked Issue is blocked (e.g. because of dependencies)
Projects
None yet
Development

No branches or pull requests

3 participants