Thanks for the feedback Franck!
Unfortunately, I haven’t found any great ways to do conditionals with inline attributes. The count parameter only works the level of the entire resource, so it’s not much help with individual items within a resource.
If you need to handle the case with a fixed number of attributes, then a really messy hack would be to create one resource for each known permutation of the attributes and set their count parameters correctly so that only one of those resources actually gets created. Think of it as an extension of the user_data_shell and user_data_cloud example in this post:
However, if you need to conditionally create a dynamic number of attributes, I don’t know of a solution