Fully-Automatic Tenant Registration Flow

[esune]

For situations such as what is described here, it would be nice to have a fully-automatic tenant approval option that will not require the innkeeper to manually approve one by one each registration request.

Acceptance Criteria:
Add an environment variable to be set at deployment time that, if present and set to true, automatically approves the tenant registration request.

The tenant will still be responsible for completing the check-in step and obtaining the credentials to access/control their agent.

[loneil]

I think this would be (in the Innkeeper plugin):

• User POSTs to /multitenancy/reservations as usual, the historical record and contact info would still be there
• That service endpoint detects some auto-approve flag and actions the same service layer call that is currently actioned by /innkeeper/reservations/{reservation_id}/approve
• The check-in password is returned back to the /multitenancy/reservations call, so in this case the body has that extra password.
• User proceeds with check-in normally for next steps to provide the password and stuff to /multitenancy/reservations/{reservation_id}/check-in

If this were to be supported in the Tenant UI would just need some tweaks to detect if the password is returned in the reservation step and appropriate screen text.
And adjust the email text instructions and info as well.

[esune]

I think we can just go with the regular check-in flow, just short-circuit the approval. The password is currently being sent out via email, isn't it? I'm looking at triggering the exact same code as the one that is executed when the approve endpoint is hit

[esune]

On second thought, I think @loneil you're right: we will probably want to display the password on-screen for immediate use.

[loneil]

I think we can just go with the regular check-in flow, just short-circuit the approval. The password is currently being sent out via email, isn't it? I'm looking at triggering the exact same code as the one that is executed when the approve endpoint is hit

Yeah exactly, that's the flow I mean in bullet point 2 above.

The password is just returned by the approve endpoint currently, so it would be returned by the 1st POST instead if this auto-flag is on.
Then the emailing is just the tenant-ui taking the password out of the result body and it's emailing, so no emails known by Traction or anything.

[loneil]

Sorry was dragging my tickets around and picked up this one, not sure if this and #587 should be in done