To clean up #cse and give a bit of power to those without Echelon access, there are two new tools to handle the A2P passcode requests.
OTP Texts:
When creating a business profile to attach Twilio A2P registrations to, Twilio requires that the contact phone number listed by the client confirm a One Time Password verification step. They have 24 hours to complete this, otherwise we have to resend the message.
The following commands allow you to resend this from a Geekbot Enabled Slack Channel, preferably the one created for this: #retry_a2p_texts
get_twilio_details:
This command gets the details of up to two Brand registrations from the site UUID you've requested. This is handy to confirm the necessity of the next command.
retry_otp:
This command checks the status up to 2 Brand Registrations, and if they're in UNVERIFIED status, it will resend the text for one or both brands.
Errors:
There are just 2 possible errors currently known.
- INVALID_UUID: If the site UUID that's used in the command doesn't exist, or is too new to have a Twilio SubAccount, it will ask you to verifiy the UUID.
- NO UNVERIFIED BRAND: If there are no brands in UNVERIFIED status it will give up, and ask you to verify the necessity. You can check this with 'get_twilio_details'
Why The Weird Command?
Dreadnought is an ancient tool that was built to integrate Geekbot with command line environments. The command is as short as I can get it because it uses Geekbot to trigger the Dreadnought integration, to trigger a command, and its arguments, which is why the command is so long; geekbot dread <command> <details>
Apologizing to Geekbot
Tradition from the olden days of yaml deploys states that one must apologize to Geekbot if triggering an avoidable error, such as deploying too soon.
If you want to avoid Geekbot's ire, please run: