[BUG] - Nebari init fails with --auth-provider custom

[sblair-metrostar]

Describe the bug

Running nebari init ... --auth-provider custom throws an error, "No registered Authentication type called custom". The --help content says this should be a valid option.

Expected behavior

Option 1. --auth-provider custom should work without error
Option 2. custom should be removed from the list of available options

OS and architecture in which you are running Nebari

Ubuntu Linux, x64

How to Reproduce the problem?

nebari init local --project-name foobar --auth-provider custom

Command output

No response

Versions and dependencies used.

Nebari: 2023.7.2.dev

Compute environment

None

Integrations

No response

Anything else?

No response

[iameskild]

@costrouc @viniciusdc is it safe to remove custom as an option? I thought there were folks who still used it, perhaps I'm misremembering.

[iameskild]

As I look at this more, I think the custom auth type can probably be removed. As for the attempt-fixes, we might be able to repurpose it as a way to by pass having the user accept the y for image upgrades, etc.

[sblair-metrostar]

As I look at this more, I think the custom auth type can probably be removed. As for the attempt-fixes, we might be able to repurpose it as a way to by pass having the user accept the y for image upgrades, etc.

Agreed. According to this code, custom authenticators were deprecated some time ago. I'll work on a PR to remove that option from the CLI so we can close this out.

[iameskild]

Thanks for following up @sblair-metrostar. I think we can move forward with removing this as an option in the CLI.