Feature Proposal: Implement `create_update_user` function for Metadata Service `gremlin_proxy`
See original GitHub issueExpected Behavior or Use Case
Currently, the function gremlin_proxy.py#create_update_user is not implemented as it is implemented for neo4j
This implementation is required when the OIDC with indexUsers
is configured, in order to create the user details.
References
Documentation reference: https://www.amundsen.io/amundsen/metadata/docs/configurations/#user_detail_method-optional
Article reference: https://www.stemma.ai/blog-post/how-to-setup-oidc-authentication-in-amundsen topic Optional: Ingest Users in metadata proxy
Issue Analytics
- State:
- Created a year ago
- Comments:5
Top Results From Across the Web
Instance metadata and user data - AWS Documentation
Access instance metadata, dynamic data, and user data to configure and manage a running Amazon EC2 instance.
Read more >Plan for managed metadata in SharePoint Server
Learn about the decisions you need to make when planning for the managed metadata service in SharePoint Server.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Turns out there are two main issues:
order by item.row_id doesn't work and
item.row_id as item_row_id order by item_row_id` does work.We are working on some small changes here
There is a lot of functionality not implemented for gremlin that is implemented in Neo4j. We are currently looking into using openCypher for Neptune not using Gremlin anymore