All the steps and configs are not shown while creating an inbox. So after creating an inbox user could be shown a link to do further setting and configs.

Problem
Right now any user with a valid auth token can retrieve any tag resource as long as they know the ID of the resource. We should return a 404 (Not found) error if someone tries to retrieve/update/delete a resource that does not have a matching account_id

Solution
In the show, update, and delete methods of the tag controller, let's add an authorize plug (middleware)

Description
As discussed cloudskiff/driftctl#334 - and documented here.

It is expected that running driftctl against a terraform state generated by an unsupported version should not be possible and be reported clearly to the user.

In the case of multiple Terraform versions inside

I'm submitting a ...

• bug report

What is the current behavior? [REQUIRED]

• If username in DB is lower-case but user used upper case to log-in, the server rejects his first packet due to ticket mismatch.

Steps to reproduce [REQUIRED]

1. Create user with lower-case (eg. helloworld)
2. Login with upper-case (eg. Helloworld)

What is the expected behavior? [REQUIRED]

User

Tailor shells out to oc, and expects a valid session (which is checked via whoami). If there is no valid session, it would be nice if Tailor would exit with a special exit code so that downstream scripts can respond well to this case.

ref opendevstack/ods-jenkins-shared-library#460

FYI @clemensutschig