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

Establish KRR as a replicated datasource in Altinn3 #176

Open
2 of 10 tasks
Tracked by #85
, #406
...
SandGrainOne opened this issue Aug 27, 2024 · 0 comments
Open
2 of 10 tasks
Tracked by #85
, #406
...

Establish KRR as a replicated datasource in Altinn3 #176

SandGrainOne opened this issue Aug 27, 2024 · 0 comments
Labels
Epic status/draft Status: When you create an issue before you have enough info to properly describe the issue.

Comments

@SandGrainOne
Copy link
Member

SandGrainOne commented Aug 27, 2024 •
edited by olebhansen
Loading

Description

Altinn 3 should have it's own copy of KRR.

Tasks
Beta Give feedback
  1. Decide if Entity Framework is to be used #189
    SandGrainOne
  2. Order a PostgreSQL server to be used by Profile #185
  3. Establish KRR DB schema #186
    SandGrainOne
  4. Get KRR credentials #195
    olebhansen
  5. Establish KRR integration #187
    1 of 4
  6. Establish KRR synch-job/trigger #188
    status/blocked
  7. Establish monitoring and ops-alerts/metrics #191
    0 of 1
    status/blocked
  8. Update profile release pipelines and helm charts #190
    SandGrainOne
  9. KRR - Define API/endpoints #192
    Ahmed-Ghanam
  10. Reorganize the Profile solution into multiple projects using typical clean architecture #194
    kind/user-story
    hggutvik

General principle: This should be possible to run in loacal-test/Docker - Check with the Registry-team to learn if they have best practices in regards to "Aspire".
@SandGrainOne SandGrainOne mentioned this issue Aug 27, 2024
Open
@SandGrainOne SandGrainOne added Epic status/draft Status: When you create an issue before you have enough info to properly describe the issue. labels Aug 27, 2024
@olebhansen olebhansen changed the title Migration of KRR data Establish KRR as datasource in Altinn3 Sep 18, 2024
@olebhansen olebhansen changed the title Establish KRR as datasource in Altinn3 Establish KRR as a replicated datasource in Altinn3 Sep 18, 2024
This was referenced Sep 20, 2024
Closed
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Epic status/draft Status: When you create an issue before you have enough info to properly describe the issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SandGrainOne