update(mysql): Move provisioner to the executable-level CredentialUsage configuration

[arunsathiya]

Overview

MySQL provisioner is moved to the executable-level CredentialUsage configuration, thus making it work only for mysql commands. MySQL Terraform provider supported, if any in the future, will use the DefaultProvisioner instead. For now, the default provisioner is set to nil.

Type of change

• Created a new plugin
• Improved an existing plugin
• Fixed a bug in an existing plugin
• Improved contributor utilities or experience

Related Issue(s)

• Relates: MySQL compatibility with Terraform #278

How To Test

• Clone this branch and run make mysql/build
• Run op plugin init mysql and set up your MySQL secrets as a 1Password item.
• Follow testing instructions as in the original MySQL work. Does the command still succeed?

Changelog

Move MySQL provisioner to the executable-level CredentialUsage configuration.

[arunsathiya]

I spent a fair amount of time trying to set up a MySQL Terraform provider but none of the three I tried seemed to work. Two issues:

• They seem to prompt for the username (despite there being a username field on the 1Password item),
• If I enter the username manually and move forward, it seems to get stuck on the database creation stage.

I am not sure why these are happening, but I attribute these to being not-fairly-regularly-maintained community providers. There was one maintained by Hashicorp but it seems to be archived now.

I can continue to take a closer look at these community-maintained providers and when one of these successfully works, and when the majority of the providers confirm to have the same environment variables, we can update the MySQL DefaultProvisioner. Until then, I propose/agree that we set it to nil.