- 20 Nov, 2018 2 commits
-
-
Lukas Burgey authored
-
Lukas Burgey authored
-
- 15 Nov, 2018 1 commit
-
-
Lukas Burgey authored
Closes #14
-
- 14 Nov, 2018 1 commit
-
-
Lukas Burgey authored
-
- 13 Nov, 2018 1 commit
-
-
Lukas Burgey authored
-
- 12 Nov, 2018 7 commits
-
-
Lukas Burgey authored
-
Lukas Burgey authored
The user of a NewDeployment can be None
-
Lukas Burgey authored
-
Lukas Burgey authored
Previously if a service had no sites and no site was manually given create_state_items failed. We now ignore such services.
-
Lukas Burgey authored
-
Lukas Burgey authored
-
Lukas Burgey authored
-
- 07 Nov, 2018 12 commits
-
-
Lukas Burgey authored
-
Lukas Burgey authored
A large step towards solving #7
-
Lukas Burgey authored
-
Lukas Burgey authored
-
Lukas Burgey authored
-
Lukas Burgey authored
-
Lukas Burgey authored
-
Lukas Burgey authored
-
Lukas Burgey authored
-
Lukas Burgey authored
Alongside other linting / minor changes.
-
Lukas Burgey authored
-
Lukas Burgey authored
-
- 29 Oct, 2018 12 commits
-
-
Lukas Burgey authored
-
Lukas Burgey authored
Related: #7
-
Lukas Burgey authored
-
Lukas Burgey authored
-
Lukas Burgey authored
-
Lukas Burgey authored
This to enable the individual key handling needed for #7.
-
Lukas Burgey authored
Partly addresses #3
-
Lukas Burgey authored
-
Lukas Burgey authored
-
Lukas Burgey authored
-
Lukas Burgey authored
-
Lukas Burgey authored
-
- 25 Oct, 2018 3 commits
-
-
Lukas Burgey authored
-
Lukas Burgey authored
This resolves #2
-
Lukas Burgey authored
The problem runs deeper than this
-
- 22 Oct, 2018 1 commit
-
-
Lukas Burgey authored
This prevents name clashes with old user instances. This was usually a problem when the upstream IdP changed the subjects of our users. The flow from here on is: When a user logs in with a changed subject a new user is created. The old user remains (but is not accessable by the user).
-