Testing #651
Merged
Testing #651
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
feat: route and api for delete user button on invite page
default model change for saving apikey - groq
…ing_message_id_dev feat: add message data retrieval endpoint with conversation and raw d…
* alerts on thumbs down * comments fixed --------- Co-authored-by: harsh mathankar <mathankarharsh31@gmail.com>
bug fix - delete user delete user from org
Owner validation before deleting
* feat: add orchestrator_history table for model execution tracking * feat: add sub_thread_id and response fields to orchestral model history schema * refactor: rename messages column to user in orchestral model history table --------- Co-authored-by: Husain Baghwala <husainhackerrank@gmail.com>
#545) * feat: add orchestrator history tracking with PostgreSQL model and API endpoints * refactor: remove unused code and whitespace from orchestrator services * refactor: rename messages field to user in orchestrator history model --------- Co-authored-by: Husain Baghwala <husainhackerrank@gmail.com>
Co-authored-by: Harsh <mathankarharsh31@gmail.com>
Co-authored-by: harsh mathankar <mathankarharsh31@gmail.com>
…re handled upstream
refactor: remove try-catch block from saveApi function since errors a…
This reverts commit 7ff3553.
…eys_update Revert "changed the redis keys"
manage the createdAt for subthread
…ess for critical operations - Updated agentVersion.routes.js to require admin role for creating, publishing, deleting, and discarding versions. - Modified apiCall.routes.js to enforce agent access for updating, deleting, and creating API calls. - Adjusted apikey.routes.js to require agent access for managing API keys. - Enhanced rag.routes.js to enforce agent access for document deletion and updates.
- Introduced folder_id assignment in middleware for requests with embedded profiles, enhancing data accessibility for downstream processing.
- Removed the check for required agent_id in the checkAgentAccessMiddleware, streamlining the middleware logic while maintaining functionality.
- Implemented a check in the checkAgentAccessMiddleware to return a 403 status with an access denial message for users with 'viewer' role, enhancing security and access control.
- Simplified the agent retrieval route by removing the checkAgentAccessMiddleware, streamlining access validation while maintaining necessary middleware for other routes.
- Updated `getAllAgentController` to include `read_only` parameter in Docstar token generation, setting it to `true` when `role_name` is 'viewer'
…n_viewer Docstar embed token viewer
- Added checkAgentAccessMiddleware to the createEmbed and updateEmbed routes to enforce access control based on user roles, enhancing security for embed operations.
- Updated the getAllAgentsInOrg function to set query.folder_id to null when folder_id is not provided, ensuring that agents without a folder_id are correctly retrieved.
- Updated the getBridgeMetrics function to dynamically select between 'daily_data' and 'fifteen_minute_data' tables based on the provided date range, improving data retrieval accuracy.
- Introduced a new field `pre_tools` of type Array in the configuration schema, with a default value of an empty array, to enhance configuration flexibility. Co-authored-by: Husain Baghwala <husainhackerrank@gmail.com>
* fix: Rename endpoint_name to title in saveApi function - Updated the saveApi function to replace the endpoint_name property with title, improving clarity in the API data structure. * feat: Implement migration to standardize API call schema to v2 format - Added migration scripts to convert existing API call documents to a unified v2 format, consolidating `endpoint_name` into `title` and removing deprecated fields. - Updated model schema to reflect new structure, including `bridge_ids`, `old_fields`, `status`, and `version`. - Enhanced documentation to outline migration behavior, examples, and rollback procedures. - Simplified service logic by eliminating runtime version handling, ensuring all API calls are now in the standardized format. * refactor: Remove API call v2 migration infrastructure and revert schema changes - Deleted MIGRATION_GUIDE.md and MIGRATION_SUMMARY.md documentation files that detailed the v2 format migration process - Removed `version` field from ApiCall model schema, reverting to previous structure - Updated test.js MongoDB connection URI to point to test database instead of production database * chore: Remove deprecated migration documentation and examples - Deleted MIGRATION_FINAL_SUMMARY.md and TITLE_MIGRATION_EXAMPLES.md files as part of the cleanup process following the removal of the `endpoint_name` field from the API schema. - This change reflects the finalization of the migration to standardize on the `title` field for API endpoint display names. * chore: Remove rollback migration script - Deleted rollback_migration.js file as part of cleanup following the finalization of the v2 migration - This script was used to revert API call schema changes by restoring old_fields backups, but is no longer needed after successful migration completion * feat: Enhance API call migration to standardize field names and clean titles - Introduced a new function `makeFunctionName` to sanitize titles by removing non-alphanumeric characters. - Updated migration logic to prioritize setting the `title` field from `endpoint_name` and `function_name`, ensuring all API calls have a valid title. - Renamed `function_name` to `script_id` across various controllers and services for consistency. - Adjusted database queries and validation schemas to reflect the new field names, improving clarity and maintainability. --------- Co-authored-by: Husain Baghwala <husainhackerrank@gmail.com>
- Removed unnecessary fields from the ApiCall model schema, including `required_fields`, `axios`, `optional_fields`, `endpoint`, and `api_description`, to streamline the data structure. - Adjusted the updateApiCalls function to eliminate the `version` field, aligning with the new schema and improving clarity in API call updates. Co-authored-by: Husain Baghwala <husainhackerrank@gmail.com>
…ancing query efficiency and structure. Updated SQL queries to reflect new field mappings and improved error handling for message retrieval and updates. (#635) Co-authored-by: Husain Baghwala <husainhackerrank@gmail.com>
…ping for image URLs, changing from a string to an array format for better clarity and consistency. (#636) Co-authored-by: Husain Baghwala <husainhackerrank@gmail.com>
Hot fix prod chnages
…iness checks. Introduced a helper function to determine if values are empty, ensuring that existing non-empty fields are preserved during updates. This improves data integrity when saving API records.
Enhance saveApi function to conditionally update fields based on empt…
#641) * feat: Add `chatbot_auto_answers` to the list of simple fields that can be updated for an agent. * feat: add chatbot_auto_answers boolean field to Configuration and BridgeVersion models --------- Co-authored-by: Husain Baghwala <husainhackerrank@gmail.com>
- Added a new `searchKnowledge` function in `rag.controller.js` to handle search requests. - Integrated Axios for making POST requests to the Hippocampus API, including necessary headers and payload. - Updated routes in `rag.routes.js` to include a new POST endpoint for search functionality. - Introduced `searchSchema` validation in `rag.validation.js` to ensure required parameters are provided.
- Changed the POST endpoint from '/search' to '/chatbot/search' in rag.routes.js to better reflect its purpose within the chatbot context. - Ensured that the middleware and validation remain intact for the updated route.
…s_funcltiy feat: Implement searchKnowledge endpoint to query Hippocampus API
…xed for web_search_filters (#643) Co-authored-by: Prayanshrajput <prayanshrajput15@gmail.com>
…#644) - Updated `apikey.controller.js` to import `new_agent_service` for dynamic model selection. - Modified AI service functions (`callAnthropicApi`, `callGroqApi`, `callMistralApi`, `callGeminiApi`, `callAiMlApi`) to accept a model parameter, allowing for more flexible API interactions. - Default models are retained for backward compatibility. Co-authored-by: Husain Baghwala <husainhackerrank@gmail.com>
…ix org_id reference in configServices - Commented out the public chatbot authentication logic in `interfaceMiddlewares.js` for clarity and potential future use. - Updated the `org_id` reference to `org_id` in `configServices.js` for consistency with the profile structure.
refactor: Clean up authentication logic in interfaceMiddlewares and f…
- Added user_id to the agentVersionData object in the createVersion function to associate the created version with the user who initiated the request. - This change enhances tracking and accountability for version management.
…_id_in_version_creation_dev
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.