Device Assurance Policies need to support dynamic fields for os_version

[raindog151]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

---

Description

Currently, the TF provider only allows for a string to be passed in to the os_version key (which automatically adds the {"minimum": } sub-object which prevents me from setting dynamic assurance values. I assume this is because it's an Early Access feature?

https://developer.okta.com/docs/api/openapi/okta-management/management/tag/DeviceAssurance/#tag/DeviceAssurance/operation/createDeviceAssurancePolicy

New or Affected Resource(s)

• okta_policy_device_assurance_android
• okta_policy_device_assurance_ios
• okta_policy_device_assurance_macos
• okta_policy_device_assurance_windows

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

References

• #0000

[raindog151]

(i am very new to using TF, so preemptive apologies for any missing data)

[duytiennguyen-okta]

OKTA internal reference https://oktainc.atlassian.net/browse/OKTA-742313

[lucascantor]

This looks like a duplicate of #1917