"Optional" fields not supported at the provider level.

[paddycarver]

When a provider's field is marked as removed, I'd expect Terraform to know not to prompt users for input on it, especially if the file is marked as optional. But in #12729, it appears that users are being prompted for input on a removed, optional field.

[mrmiyagi]

yep, can't manage any google cloud resources!

[jbardin]

@paddyforan, I think I see the difference here. All other uses of Removed are in resources, this is the only one that is at a provider level.

Turns out that that schema.Provider doesn't support Optional right now.

[paddycarver]

So is Removed not supported at the provider level? If not, is there a technical or UX reason it can't be? I guess the better question is: do we consider Removed not preventing Terraform from prompting for input a bug, or do we just consider Optional not preventing Terraform from prompting for input a bug? (Or both, I suppose?)

[jbardin]

No, Removed technically is working just fine.

Optional is not working, so it will always prompt, or if there was a default, it would fail to validate.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.