IDSEC-000: Fix missing types on converters

Author: CyberarkReleaser

VERSION

@@ -1 +1 @@
-0.1.11
+0.1.12

docs/guides/creating_sia_rdp_strong_accounts.md

@@ -48,7 +48,7 @@ The workflow demonstrates creating strong accounts for different scenarios:
 - Domain administrator accounts
 - Accounts with different credential formats
 
-## Basic Strong Account (Local Admin)
+### Basic Strong Account (Local Admin)
 
 main.tf
 ```terraform
@@ -123,7 +123,7 @@ variable "secret_description" {
 
 ---
 
-## Domain Administrator Strong Account
+### Domain Administrator Strong Account
 
 main.tf
 ```terraform
@@ -202,7 +202,7 @@ variable "secret_description" {
 
 ---
 
-## Privilege Cloud Account Reference
+### Privilege Cloud Account Reference
 
 For production environments, reference credentials stored in Privilege Cloud:
 
@@ -281,7 +281,7 @@ variable "secret_description" {
 
 ---
 
-# Username Format Examples
+## Username Format Examples
 
 The `provisioner_username` field supports various formats:
 
@@ -294,9 +294,9 @@ The `provisioner_username` field supports various formats:
 
 ---
 
-# Managing Account Lifecycle
+## Managing Account Lifecycle
 
-## Rotating Credentials
+### Rotating Credentials
 
 Update the password by changing the `provisioner_password`:
 
@@ -316,7 +316,7 @@ resource "idsec_sia_secrets_vm" "admin_account" {
 
 ---
 
-# Best Practices
+## Best Practices
 
 1. **Use descriptive names**: Include purpose or environment in `secret_name` (e.g., `Prod-WebServers-RDP`)
 2. **Use PCloudAccount for production**: Leverage Privilege Cloud's password rotation and audit features
@@ -325,15 +325,15 @@ resource "idsec_sia_secrets_vm" "admin_account" {
 
 ---
 
-# Related Resources
+## Related Resources
 
 - [Creating RDP Target Sets](creating_sia_rdp_target_sets.md) - Associate strong accounts with Windows targets
 - [Managing RDP Target Sets and Secrets](managing_rdp_target_sets_and_secrets.md) - Comprehensive management guide
 - [Provisioning RDP Access](provisioning_rdp_access.md) - End-to-end RDP access setup
 
 ---
 
-# Additional Information
+## Additional Information
 
 For more details on the resources used in this workflow:
 

internal/schemas/schemas_common_converters.go

@@ -238,10 +238,17 @@ func attrToInterface(key string, val attr.Value, prototype interface{}) (interfa
 	switch v := val.(type) {
 	case types.String:
 		return v.ValueString(), nil
+	case types.Number:
+		value, _ := v.ValueBigFloat().Float64()
+		return value, nil
+	case types.Int32:
+		return v.ValueInt32(), nil
 	case types.Int64:
 		return v.ValueInt64(), nil
 	case types.Bool:
 		return v.ValueBool(), nil
+	case types.Float32:
+		return v.ValueFloat32(), nil
 	case types.Float64:
 		return v.ValueFloat64(), nil
 	case types.Object:

templates/guides/creating_sia_rdp_strong_accounts.md

@@ -48,7 +48,7 @@ The workflow demonstrates creating strong accounts for different scenarios:
 - Domain administrator accounts
 - Accounts with different credential formats
 
-## Basic Strong Account (Local Admin)
+### Basic Strong Account (Local Admin)
 
 main.tf
 ```terraform
@@ -115,7 +115,7 @@ variable "secret_description" {
 
 ---
 
-## Domain Administrator Strong Account
+### Domain Administrator Strong Account
 
 main.tf
 ```terraform
@@ -186,7 +186,7 @@ variable "secret_description" {
 
 ---
 
-## Privilege Cloud Account Reference
+### Privilege Cloud Account Reference
 
 For production environments, reference credentials stored in Privilege Cloud:
 
@@ -257,7 +257,7 @@ variable "secret_description" {
 
 ---
 
-# Username Format Examples
+## Username Format Examples
 
 The `provisioner_username` field supports various formats:
 
@@ -270,9 +270,9 @@ The `provisioner_username` field supports various formats:
 
 ---
 
-# Managing Account Lifecycle
+## Managing Account Lifecycle
 
-## Rotating Credentials
+### Rotating Credentials
 
 Update the password by changing the `provisioner_password`:
 
@@ -292,7 +292,7 @@ resource "idsec_sia_secrets_vm" "admin_account" {
 
 ---
 
-# Best Practices
+## Best Practices
 
 1. **Use descriptive names**: Include purpose or environment in `secret_name` (e.g., `Prod-WebServers-RDP`)
 2. **Use PCloudAccount for production**: Leverage Privilege Cloud's password rotation and audit features
@@ -301,15 +301,15 @@ resource "idsec_sia_secrets_vm" "admin_account" {
 
 ---
 
-# Related Resources
+## Related Resources
 
 - [Creating RDP Target Sets](creating_sia_rdp_target_sets.md) - Associate strong accounts with Windows targets
 - [Managing RDP Target Sets and Secrets](managing_rdp_target_sets_and_secrets.md) - Comprehensive management guide
 - [Provisioning RDP Access](provisioning_rdp_access.md) - End-to-end RDP access setup
 
 ---
 
-# Additional Information
+## Additional Information
 
 For more details on the resources used in this workflow: