We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
private
ssl_server_key
There is an issue in the handling of the hashed private value in the ssl_server_key resource.
The API response from the endpoint /api/tm/8.3/config/active/ssl/server_keys/{Id} returns a base64-encoded hashed key. Since there is a DiffSuppressFunc set which swallows the diff (https://github.com/pulse-vadc/terraform-provider-vtm/blob/master/8.3/resource_ssl_server_key.go#L50), and the object is fetched new from the API on Update (https://github.com/pulse-vadc/terraform-provider-vtm/blob/master/8.3/resource_ssl_server_key.go#L120), the private key is always sent back to the API as a base64-encoded hashed key. This key is persisted to the configuration and results in the error Unknown key type on the vTM.
/api/tm/8.3/config/active/ssl/server_keys/{Id}
DiffSuppressFunc
Update
Unknown key type
Applying terraform again fixes this problem, because the file hash has changed in the API and Terraform detects this as a diff correctly.
Steps to reproduce:
note
The text was updated successfully, but these errors were encountered:
No branches or pull requests
There is an issue in the handling of the hashed
private
value in thessl_server_key
resource.The API response from the endpoint
/api/tm/8.3/config/active/ssl/server_keys/{Id}
returns a base64-encoded hashed key. Since there is aDiffSuppressFunc
set which swallows the diff (https://github.com/pulse-vadc/terraform-provider-vtm/blob/master/8.3/resource_ssl_server_key.go#L50), and the object is fetched new from the API onUpdate
(https://github.com/pulse-vadc/terraform-provider-vtm/blob/master/8.3/resource_ssl_server_key.go#L120), the private key is always sent back to the API as a base64-encoded hashed key. This key is persisted to the configuration and results in the errorUnknown key type
on the vTM.Applying terraform again fixes this problem, because the file hash has changed in the API and Terraform detects this as a diff correctly.
Steps to reproduce:
ssl_server_key
resourcenote
valueUnknown key type
error in the vTMprivate
attribute needs to be updatedThe text was updated successfully, but these errors were encountered: