Open smithjw opened 1 week ago
Another issue with the validation that I run into is differences in indentation ("incorrect indentation on line 4"), and the modification of attributes in profiles.
Many of my profiles have <string />
in the body, which is replaced with <string></string>
.
I can confirm that the data
value's new lines are the issue. I've been able to work around it by removing them (programmatically, prior to apply, so as to preserve the neat formatting in repo).
Indentation, empty values' key style, and trailing new lines are also three annoyances I can confirm (and which I've also programmatically worked around).
@w0de , what steps are you taking ?
When trying to create a Configuration Profile in Jamf Pro that contains a Certificate payload, I consistently receive
plist line count mismatch
errors during planning. In the past these errors have been generated because by default all files within my repo have a blank last line (added by VS Code). Prior to the formatting changes in thejamfpro_macos_configuration_profile_plist
, I was able to mitigate this by wrapping the file object within the resource in achomp()
function but this no longer works as the line discrepancy is often quite large.I believe this could be due to the formatting of the profile placing the
data
value all on one line rather than my formatted block within the mobile config file.And just to confirm, this mobileconfig file example uploads and displays in Jamf without error.
profile.tf
example.mobileconfig