Reinstate Confluence Search Plugin in Harness IDP
planned
C
Cooing Rook
The Confluence Search Plugin, previously available, has not been migrated to the new Backstage Backend system. As a result, teams are unable to access Confluence content directly within the IDP, impacting productivity and ease of access to documentation.
Why It Matters:
Accessing Confluence content seamlessly within Harness IDP is critical for enabling teams to find documentation quickly and efficiently. The lack of this feature has been highlighted as a pain point by several teams, who now need to leave the platform to search for resources externally.
Request:
- Coordinate with the plugin owners to assess the feasibility of migrating the Confluence Search Plugin to the new Backstage Backend system.
- If external plugin owners cannot provide support, consider implementing an internal solution to restore this functionality based on team needs.
Impact if Addressed:
- Improves developer productivity by centralizing access to Confluence documentation within Harness IDP.
- Enhances user experience by reducing the need to switch between tools, keeping workflows streamlined.
Log In
Rashmi Hegde
We have been working to build a more native plugin infrastructure that gives Harness the ability to leverage the platform more extensively (RBAC, AI based search etc)
Are the confluence pages part of Docs in Catalog (through confluence connector integration) or Catalog components? We do have search available in both now. Would love to understand if this is still a problem and what we can do to solve
Himanshu Mishra
marked this post as
planned