When to implement service.go and connection_config.go?

[51stpage]

Hi,

I've noticed that a number of services, usually the bigger complex ones like aws, azure, gcp, etc have service.go and connection_config.go files. However, for smaller services such as whois or rss, these files are missing. When would I need to implement service.go? How is that implementation used? Does this have something to do with running Steampipe as a local service? I'm working on plugin for a stateless API and it's tricky to figure out what I do and don't need to implement.

I didn't see anything about Services or Connection Config in the Developers guide to writing plugins. Did I miss something? https://steampipe.io/docs/develop/writing-plugins

[e-gineer]

It really depends on the complexity of the plugin. We commonly use those files in more complex plugins for:

• connection_config.go defines the connection options, e.g. token or regions or similar.
• service.go breaks out service connection setup code, rather than simpler plugins that keep it in utils.go.

It's really up to the plugin on the best way to arrange these internal files, but our turbot/steampipe-plugin-* code is definitely good as examples, and should be fairly consistent.

Hope that helps!