User is able to start creating a policy with no repository created

[cuff-links]

Environment

Kibana: 7.5.0 BC7
Elasticsearch 7.5.0 BC 7
Browsers: Firefox and Chrome (Both latest)

Preconditions:
Ensure you have no snapshots, policies or repositories created.

Steps to reproduce:
1.) Navigate to Snapshot and Restore
2.) Navigate to the policies tab

Expected Result:
A message telling you that there are no repositories created and and a button for you to create one.

Actual Result:
Create a New policy button which works and lets you go try to create one.

[elasticmachine]

Pinging @elastic/es-ui (Team:Elasticsearch UI)

[alisonelizabeth]

@cuff-links thanks for opening this!

I'm going to change this to an enhancement. We do alert the user that there are no repositories when they go into the create flow.

If we want to alert them one step sooner on the policies page (as you suggest), we would need to make an additional request on the policies page to fetch the repositories to see if any exist. We also need to consider the best UI/UX. I think it's straightforward if the user has no policies set up. But, you could also end up in this situation if a repo(s) was deleted with existing policies (relates to #46791).

[cuff-links]

@alisonelizabeth Can a policy be created independent of a repository? If not, we shouldn't let them start creating something that depends on a repository without one being configured. Also, in the creation flow, a user can just skip past that warning as the next button is still enabled as pointed out in #51397.

[cuff-links]

If a repository is not optional, i think it would be good UX to point the user to the Repo page just as we do in the snapshots tab. That would be consistent.

[alisonelizabeth]

I'm going to close this for now. While it may be more optimal to show a prompt before clicking into the policy wizard, I think the current UI still makes it clear that a repository must be registered first.

Also, in the creation flow, a user can just skip past that warning as the next button is still enabled as pointed out in #51397.

I agree this is a valid bug. Let's address it via #51397.