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.

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

Feature/writable api #50

Merged
merged 3 commits into from
Feb 25, 2025
Merged

Feature/writable api #50

merged 3 commits into from
Feb 25, 2025

Conversation

jnation3406
Copy link
Member

These changes should make all the data structures within configdb fully writable via the API. This was requested from a user in these issues:

observatorycontrolsystem/ocs_example#22
observatorycontrolsystem/ocs_example#24

The only change from the read API is the addition of some id fields to the optical element, optical element group, generic mode, generic mode group, and configuration type properties output. I also updated the simple index page to link to all the data structures API results.

@jnation3406 jnation3406 requested a review from Fingel February 7, 2025 20:42
Copy link

@jchate6 jchate6 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will this require updates for the LCO observing portal or developers docs?

@jnation3406
Copy link
Member Author

@jchate6 Yes, it would be good to add something to the OCS docs with examples of how to setup configdb via the API. I'll plan to add that. I don't think the developer docs need to be updated since the read API should be returning the same things and apparently we already had ids in those docs even if they weren't being returned before. But maybe it would be worth calling out some of the different field names for the write_only fields for the writable part of the API there too.

@jnation3406 jnation3406 merged commit ab99478 into main Feb 25, 2025
10 checks passed
@jnation3406 jnation3406 deleted the feature/writable_api branch February 25, 2025 00:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants