google provider google_storage_bucket Documentation BUG for days_since_custom_time

[mike-19]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.
• If an issue is assigned to the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.

Documentation BUG

This is a documentation error as per the discussions here [1]
This seems to be a bug in the Google provider documentation. The source code shows that the type is an integer

terraform-provider-google/google/resource_storage_bucket.go

Lines 171 to 175 in 3ebd09f

	"days_since_custom_time": {
	Type: schema.TypeInt,
	Optional: true,
	Description: `Number of days elapsed since the user-specified timestamp set on an object.`,
	},

Please correct the documentation references, google provider documentation has the wrong format described [3] instead a number of days its referencing Date in RFC 3339

[1]https://discuss.hashicorp.com/t/query-on-resource-google-storage-bucket/24953/2

[3]https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/storage_bucket#days_since_custom_time

Affected Resource(s)

• google-storage-bucket

[rileykarson]

Note: While the source code appears to have the right docs, the registry seems to be off.

[github-actions]

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.