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

Update database schema #122

Closed
1 task done
PhlppKrmr opened this issue May 24, 2023 · 3 comments
Closed
1 task done

Update database schema #122

PhlppKrmr opened this issue May 24, 2023 · 3 comments
Assignees
@njochens
Labels
documentation Improvements or additions to documentation refactoring Refactoring of old features REQ.8 Each proxy should write into it’s dedicated database.
Milestone
Sprint 08

Comments

@PhlppKrmr
Copy link
Contributor

PhlppKrmr commented May 24, 2023 •
edited by njochens
Loading

User story

  1. As a developer
  2. I want / need an updated database schema
  3. So that it natches the Kubernetes API

Acceptance criteria

  • Kubernetes API and database schema match

Linked Issues

Additional information

  • none

Definition of done (DoD)

DoD general criteria

  • Feature has been fully implemented
  • All acceptance criteria were met
  • Product owner approved features
  • All tests are passing
  • Pull request to "develop" branch is merged & closed
  • Bill of materials is updated with new dependencies
@PhlppKrmr PhlppKrmr added documentation Improvements or additions to documentation approved REQ.8 Each proxy should write into it’s dedicated database. refactoring Refactoring of old features labels May 24, 2023
@PhlppKrmr PhlppKrmr moved this to Product Backlog in amos2023ss04-feature-board May 24, 2023
@jandegen jandegen moved this from Product Backlog to Sprint Backlog in amos2023ss04-feature-board May 24, 2023
@PhlppKrmr PhlppKrmr added this to the Sprint 06 (Mid-Release) milestone May 24, 2023
@jandegen
Copy link
Contributor

First changes with watcher implementation, needs further implementation

@jandegen jandegen moved this from Sprint Backlog to Product Backlog in amos2023ss04-feature-board May 31, 2023
@PhlppKrmr PhlppKrmr moved this from Product Backlog to Sprint Backlog in amos2023ss04-feature-board May 31, 2023
@njochens njochens self-assigned this Jun 2, 2023
@njochens njochens moved this from Sprint Backlog to In Progress in amos2023ss04-feature-board Jun 2, 2023
@jandegen jandegen removed the approved label Jun 5, 2023
@njochens
Copy link
Contributor

njochens commented Jun 7, 2023

Excel with Kubernetes API representation is uploaded to confluence and can be updated with new approaches for the scheme. For example what fields should be imported and if they should, as a special field in PostgreSQL or as plain JSON?

@jandegen jandegen moved this from In Progress to Product Backlog in amos2023ss04-feature-board Jun 7, 2023
@jandegen jandegen moved this from Product Backlog to Sprint Backlog in amos2023ss04-feature-board Jun 7, 2023
@PhlppKrmr PhlppKrmr modified the milestones: Sprint 07, Sprint 08 Jun 7, 2023
@njochens njochens moved this from Sprint Backlog to In Progress in amos2023ss04-feature-board Jun 14, 2023
@jandegen
Copy link
Contributor

Scheme specified and documented. Changes will be applied once feature implementationr requires it.

@jandegen jandegen moved this from In Progress to Awaiting Review in amos2023ss04-feature-board Jun 14, 2023
@PhlppKrmr PhlppKrmr moved this from Awaiting Review to Feature Archive in amos2023ss04-feature-board Jun 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@njochens njochens

Labels
documentation Improvements or additions to documentation refactoring Refactoring of old features REQ.8 Each proxy should write into it’s dedicated database.
Projects
amos2023ss04-feature-board
Status: Feature Archive
Milestone
Sprint 08
Development

No branches or pull requests
3 participants
@PhlppKrmr @njochens @jandegen