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

Add Code Graph Secret Alias for GraphRAG API Integration #2535

Conversation

MirzaHanan
Copy link
Contributor

@MirzaHanan MirzaHanan commented Feb 10, 2025

Describe the Changes:

  • Add secret alias to code graph payload for GraphRAG API authentication in chat and ticket handlers

Daily Bounty: https://community.sphinx.chat/bounty/3630

Issue ticket number and link:

Checklist before requesting a review

  • I have performed a self-review of my code
  • I have tested on Chrome
  • New feature (non-breaking change which adds functionality)
  • I have provided a screenshot and demo of changes in my PR

@@ -486,7 +493,7 @@ func (th *ticketHandler) PostTicketDataToStakwork(w http.ResponseWriter, r *http
"sourceWebsocket": ticketRequest.Metadata.ID,
"webhook_url": webhookURL,
"phaseSchematic": schematicURL,
"codeGraph": codeGraphURL,
"codeGraph": codeGraphData,
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we ensure that the output to stackwork adds the alias as a seperate alias.

We should retain codeGraph as:

"codeGraph": codeGraphURL,

and add in a seperate field"

"codeGraphAlias": codeGraph.SecretAlias,

image

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@humansinstitute I fix it

@MirzaHanan
Copy link
Contributor Author

@humansinstitute Please review here #2537

@MirzaHanan MirzaHanan closed this Feb 11, 2025
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