This issue is a list of bugs for the same resource: sase_objects_hip_objects
When using nested parameter tree: anti_malware → criteria → last_scan_time → product_version
The parameter expects a string, but the response from the API is an integer.
╷
│ Error: Error in create
│
│ with module.hip_with_tfvars.sase_objects_hip_objects.this["terraform-hip-ms-as"],
│ on ../../modules/hip/main.tf line 1, in resource "sase_objects_hip_objects" "this":
│ 1: resource "sase_objects_hip_objects" "this" {
│
│ json: cannot unmarshal number into Go struct field ProductVersionObject.anti_malware.criteria.product_version.greater_equal of type string
When using nested parameter tree: anti_malware → criteria → virdef_version → within OR not_within → days OR versions
both are being enforced at the same time, but the API requires an either or, not both together.
When using nested parameter tree: disk_encryption → criteria → encrypted_locations → encrypted_state → is OR is_not
Both values are being enforced with defaults, but the API requires an either or, not both together
When using nested parameter tree: host_info → criteria → domain → os → contains
All vendor keys are being enforced with defaults, but the API requires an either or, not both together.
When using nested parameter tree: disk_backup → criteria → last_backup_time → within → days OR hours
both are being enforced at the same time, but the API requires an either or, not both together.
Expected behavior
Set parameter field as integer instead of string
Do not enforce defaults
Do not enforce defaults
Do not enforce defaults
Do not enforce defaults
Current behavior
Can not use current parameters within the respective criteria due to enforced defaults that cause creation errors.
Possible solution
Steps to reproduce
1.
5.
6.
7.
Screenshots
Context
Your Environment
Version used:
Environment name and version (e.g. Chrome 59, node.js 5.4, python 3.7.3):
Describe the bug
This issue is a list of bugs for the same resource: sase_objects_hip_objects
When using nested parameter tree: anti_malware → criteria → last_scan_time → product_version
The parameter expects a string, but the response from the API is an integer.
When using nested parameter tree: anti_malware → criteria → virdef_version → within OR not_within → days OR versions
both are being enforced at the same time, but the API requires an either or, not both together.
When using nested parameter tree: disk_encryption → criteria → encrypted_locations → encrypted_state → is OR is_not
Both values are being enforced with defaults, but the API requires an either or, not both together
When using nested parameter tree: host_info → criteria → domain → os → contains
All vendor keys are being enforced with defaults, but the API requires an either or, not both together.
When using nested parameter tree: disk_backup → criteria → last_backup_time → within → days OR hours
both are being enforced at the same time, but the API requires an either or, not both together.
Expected behavior
Current behavior
Can not use current parameters within the respective criteria due to enforced defaults that cause creation errors.
Possible solution
Steps to reproduce
1. 5. 6. 7.
Screenshots
Context
Your Environment