The env attribute cannot be specified as an attribute of a struct

[PrimaryCY]

Preflight Checklist

• I have searched the issue tracker for an issue that matches the one I want to file, without success.
• I am not looking for support or already pursued the available support channels without success.
• I have checked the troubleshooting guide for my problem, without success.

Viper Version

1.15.0

Go Version

1.17.8

Config Source

Environment variables

Format

Other (specify below)

Repl.it link

No response

Code reproducing the issue

func main(){
        type C struct {
		HOME string `mapstructure:"HOME"`
	}

	c := C{}

	viper.AutomaticEnv()
	err := viper.Unmarshal(&c)
	if err != nil {
		panic(err)
	}
	fmt.Println(c.HOME)
	fmt.Println(viper.Get("HOME"))

}

Expected Behavior

I want to get the value of home from the structure
output:
/Users/cy
/Users/cy

Actual Behavior

output:

/Users/cy

Steps To Reproduce

computer:
macOS Catalina version: 10.15.7(19h15)
MacBook Pro (15-inch, 2018)

Additional Information

No response

[github-actions]

👋 Thanks for reporting!

A maintainer will take a look at your issue shortly. 👀

In the meantime: We are working on Viper v2 and we would love to hear your thoughts about what you like or don't like about Viper, so we can improve or fix those issues.

⏰ If you have a couple minutes, please take some time and share your thoughts: https://forms.gle/R6faU74qPRPAzchZ9

📣 If you've already given us your feedback, you can still help by spreading the news,
either by sharing the above link or telling people about this on Twitter:

https://twitter.com/sagikazarmark/status/1306904078967074816

Thank you! ❤️

[twgcode]

I've also encountered this issue, and I've currently resolved it by using viper.BindEnv("HOME"). However, this doesn't seem very user-friendly. Could you please confirm if this bug has been fixed? I'm currently using Go 1.20.3 and Viper v1.17.0.