chore: deprecate type field for boundary_account_ldap #400
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
boundary_account_ldap
resource has a requiredtype
field but the only valid value is "ldap". Deprecating thetype
field and setting a default value ofldap
.Users will still be able to pass in a value for the
type
field. This will prevent existing configs from breaking.Example: The missing
type
field will default toldap
.A similar change for
boundary_account_password
: #396