Hiding extension frontend but using extensionv2 functionality

Blue Robotics Software BlueOS
1

Hey,

I am developing an extension and I want it to be available under the /extensionv2 url but I don’t want it to show up in the sidebar. I have created a register_service endpoint which has the "works_in_relative_paths" option set to true. From the docs:

  • "works_in_relative_paths" (optional, New in 1.4)
  • Boolean (true/false) specifying whether the extension can be served at an arbitrary base URL >(i.e. it does not access its resources using absolute paths)
  • This is required for extensions to be accessible remotely (e.g. via a cloud proxy), and is >recommended for all extensions
  • Makes the extension available at /extensionv2/<sanitized_name>/
  • The sanitized name is the name field in lowercase, with all non alphanumeric characters > removed

This works great but now I have a backend extension which has a frontend icon (like the Cockpit extension in this image) but I don’t want an icon because the extension doesn’t need to have frontend functionality.

image
image247×276 9.17 KB

My question: Is it possible to serve an extension under /extensionv2, by setting the "works_in_relative_paths" option, and not have a frontend icon show in BlueOS?

2

Hi @rutger-seascape,

Interesting question - not a use-case we’ve considered before, but it does make sense. It’s not supported behaviour at the moment, but it seems reasonable to add a new option for it (e.g. hide_from_sidebar or similar), though understandably that will only work in new versions of BlueOS.

There’s some possibility there’s a way of making an existing configuration that’s broken in just the right way that the existing system works for the URL but fails to create a sidebar listing, but that’s not something we can spend time looking for or trying to support :sweat_smile:

3

Thanks for your reply. Ah alright, good to know. I now just serve an empty index.html as a solution.