"Backend not yet configured" Behavior

For auth backends, if you click on it you get "This backend is not yet configured" and directed to the configuration page with the "Manage Roles" tab being greyed out and unclickable. Like the code:

vault-ui/app/components/Authentication/Aws/Aws.jsx

Lines 139 to 142 in 35ab0d0

    
           error.message = `This backend has not yet been configured`; 
        
           history.push(`${this.state.baseUrl}backend`); 
        
           this.setState({ selectedTab: 'backend', isBackendConfigured: false }); 
        
           snackBarMessage(error);

Some auth backends though, like Aws/Aws-ec2 do not specifically need configured if using the vault instance role. There is no configuration that needs to be set for it work properly.

If you click "save" without actually making any changes, it unlocks the "Manage Roles" tab and works as expected but this took me a while to figure out. Could the behavior of this be changed so that maybe "Manage Roles" is not greyed out? I would be fine putting in the PR if you have a solution to this bug.

	error.message = `This backend has not yet been configured`;
	history.push(`${this.state.baseUrl}backend`);
	this.setState({ selectedTab: 'backend', isBackendConfigured: false });
	snackBarMessage(error);