-
Notifications
You must be signed in to change notification settings - Fork 2
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
Refactor deprecated fields and messages #18
Conversation
Deprecated fields and messages are wildly inconsistent. Several deprecated fields are not marked as such and the documention is not laid out consistently. This commit should bring them all in line.
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.
@ismirlia Deprecating field should be remove since we have had the deprecated for a while and if Service Broker doesn't support them anymore. If SB still has support for them, then we should list them as deprecated.
Ok let's have this PR remove these fields then. |
According to the code the entire ibm_pi_network_port resource is deprecated in favor of the ibm_pi_network_port_attach resource. Can I just go ahead and remove those files also? @michaelkad |
…bm/terraform-provider-ibm into deprecated-message-consistency
Opened this in the main terraform repo so closing this. |
Deprecated fields and messages are wildly inconsistent. Several deprecated fields are not marked as such and the documentation is not laid out consistently. This pull request should bring them all in line.