Remove deployed field from ConfigurationModel #8252
Assignees
Comments
11 tasks
inmantaci
pushed a commit
that referenced
this issue
Oct 24, 2024
# Description closes #8189 - [x] we no longer set the deploy done field, spin out remove to other ticket #8252 - [x] spin out ticket to read status of requires from scheduler instead of DB #8253 # Self Check: Strike through any lines that are not applicable (`~~line~~`) then check the box - [x] Attached issue to pull request - [x] Changelog entry - [x] Type annotations are present - [x] Code is clear and sufficiently documented - [x] No (preventable) type errors (check using make mypy or make mypy-diff) - [x] Sufficient test cases (reproduces the bug/tests the requested feature) - [x] Correct, in line with design - [ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: ) - [ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see [test-fixes](https://internal.inmanta.com/development/core/tasks/build-master.html#test-fixes) for more info)
|
Hey team! Please add your planning poker estimate with Zenhub @arnaudsjs @hlloreda @Hugo-Inmanta @jptrindade @sanderr |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the ConfigurationModel class (which is both DTO and DAO) we have the fields
These are surprisingly difficult to set, as they require going over all resources
I don't think they are used anymore
We should drop these fields
May affect inmanta-cli, see e.g. quickstart-lsm
The text was updated successfully, but these errors were encountered: