There is a blog post on generic HTTP connectors

[izgeri]

There is blog post that:

• Explains briefly what Secretless is
• Explains what the generic HTTP connector is, and why you might use it
• Explains how to write a config for the generic HTTP connector for a specific API
• Shares that we have built a library of example generic HTTP connector configs for many common target APIs
• Discuss how some APIs weren’t a good fit for the generic HTTP connector, and how to tell if your API is a good fit
  • Example: Google maps API (which we were able to resolve by expanding the capabilities of the generic HTTP connector to include support for injecting query parameters - HTTP Generic Connector supports URL parameter injection #1290)
  • Example: Twitter oauth1 (not yet able to resolve, but maybe we could if the generic HTTP connector supported the required hashing methods, or we could write it as a standalone connector - Generic HTTP Config supports OAuth1 #1297)
  • Example: Docker CLI to connect to remote docker registry (not yet able to resolve, may create a standalone connector - Create a Docker CLI Connector for Secretless #1312)
• If possible, talk about how to resolve cases that aren’t a good fit by expanding the generic HTTP connector or by writing a custom HTTP connector.

If we've completed the following issues by the time of publishing, it might also be nice to refer to those in the post:

• Write the google maps generic HTTP connector config - There is an example generic HTTP connector config for the Google Maps API #1259
• Create an oauth1 and/or docker HTTP connector