-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: officially deprecate the metal_device_network_type resource #773
Conversation
30da0de
to
a666c49
Compare
a666c49
to
c343b92
Compare
@@ -2,7 +2,10 @@ | |||
subcategory: "Metal" | |||
--- | |||
|
|||
# equinix_metal_device_network_type (Resource) | |||
# equinix_metal_device_network_type (Resource, Deprecated) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There doesn't seem to be a standard for marking entire resources as deprecated in the docs. The HashiCorp recommendations are focused only on the code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually the differentiation between resource / datasource in parentheses seems to be a thing of the past, I don't see it in the documentation of any other provider. For me it's fine like this, but the documentation generation plugin won't put things like that either if we stop using templates in the future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So the Note below might be enough, but again, I think the way you put it seems clarifying
c343b92
to
a6cc80a
Compare
a6cc80a
to
7cb3405
Compare
7cb3405
to
ea43726
Compare
No description provided.