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
Issue 247 generic asset crud #290
Conversation
… steps forward for use cases not covered yet by auth policy
…eady defines what happens)
…g the need for issue#200); fix modelling problem if several distinct principal formulations exist for one permission
…ets when we don't already have them (distinguish by name); re-add old asset tests;
…r name+account_id
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I request small changes mostly.
The bigger issue is that we need some sensor CRUD (at least the R) before we can update our documentation. In particular, we are missing a sensor listing where users can look up entity addresses, so they can actually use the data API.
@@ -17,6 +17,11 @@ | |||
from flexmeasures.api.common.responses import required_info_missing | |||
|
|||
|
|||
""" | |||
Deprecated. Use /api/dev/generic_assets. | |||
TODO: Can/should we add a deprecation warning to responses? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. At the very least in the documentation of the relevant endpoints.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should also discuss updating documentation before releasing.
Maybe the easiest path towards releasing this is to a listing of sensors on each asset page. Later, we can link from there to a sensor page where you can see a plot and find a link to edit its meta data or delete it. Those are less crucial for now. |
I agree. |
Signed-off-by: Nicolas Höning <nicolas@seita.nl>
-e Signed-off-by: Nicolas Höning <nicolas@seita.nl>
Signed-off-by: Nicolas Höning <nicolas@seita.nl>
Signed-off-by: Nicolas Höning <nicolas@seita.nl>
Signed-off-by: Nicolas Höning <nicolas@seita.nl>
Signed-off-by: Nicolas Höning <nicolas@seita.nl>
Signed-off-by: Nicolas Höning <nicolas@seita.nl>
Signed-off-by: Nicolas Höning <nicolas@seita.nl>
Signed-off-by: Nicolas Höning <nicolas@seita.nl>
Signed-off-by: Nicolas Höning <nicolas@seita.nl>
Remove the entity addresses from the generic asset listing, and list the number of sensors instead. * grammar Signed-off-by: F.N. Claessen <felix@seita.nl> * Update generic asset listing, replacing entity addresses with number of sensors Signed-off-by: F.N. Claessen <felix@seita.nl> * Avoid crashing on formatting None values Signed-off-by: F.N. Claessen <felix@seita.nl> * Fix wrong variable name Signed-off-by: F.N. Claessen <felix@seita.nl> * Fix incorrect type annotation Signed-off-by: F.N. Claessen <felix@seita.nl> * Partly revert cefe320 Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: Nicolas Höning <nicolas@seita.nl>
Signed-off-by: Nicolas Höning <nicolas@seita.nl>
Signed-off-by: Nicolas Höning <nicolas@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for all the help moving our asset crud over! It seems project 9 is about finished.
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
… to fm1 scheme. Signed-off-by: F.N. Claessen <felix@seita.nl>
Also:
For testing: try if the UI Asset Crud is doing its job. It is using the generic asset API internally.
TODO: