Here's what the second one looks like:

object MyObject : SomeDependencyInterface {
  // ...
}

@Configuration
class RegisterMyObject {
  @Bean
  fun myObject() = MyObject
}

Ultimately, I'm wondering if there's a way to ditch the

@Configuration

class and just register my object as a

@Component

.

#2 is fine, it's not a huge amount of extra code and does the job. I was just seeing if there was a way to make it even simpler so that if this gets replicated to other projects, there's less boilerplate in those cases.

The reason it's an object is to be able to call all of the stuff inside it (a bunch of constants and nested constants in child objects). The reason it's a bean is that it implements an interface that registers said constants with an external service. It's part of a feature flag system. The same class is used to tell the external "Feature Flag service" which flags exist and to also give the internal code a simple API to access said flags.

Ofcourse this also means that anywhere you want to inject this object, will need to inject based on

SomeDependencyInterface

and not

MyObject

.