Add Versioning to Items Import from GitHub

I would like to see versioning enabled for Intune policies import using GitHub. It can have no comment on the version, but it appears right now that the entire versioning structure is ignored. Perhaps the version could be incremented any time that file gets updated by default or someone could override that by using a metadata structure similar to the scripted actions where we define the description, execution mode, etc. in comments at the top? 

Our goal is to have all our Intune policies defined in source control but ability to create baselines in NMM that we can deploy as a package based on versioning to clients at onboarding. Versioning is a want to have feature.

1

Comments (2 comments)

0
Avatar
Dave Stephenson

Are you wanting it to be like the GUI Version where you're able to see the different versions (possible include the date of the change?) and choose the one you're wanting?
Or did you have something else in mind?
You mentioned being able to set the metadata like a scripted action so I'm not too certain what you'd want to do with that as part of the Intune Policy/Deployment.
Could you possibly elaborate on that?

 

0
Avatar
Jacob Reinhardt

I would like to be able to choose the versions like in your first screenshot in the context of what version I am assigning to a customer or to a baseline. It seems that these two features are already provided when the policies are not import using GitHub. Thus, the goal is feature parity between the two. We know that we will have blame tracking via GitHub, but it seems there are features in Nerdio that would benefit that we would lose.

The reference to Scripted Actions was a comparison to how this feature would work. in Scripted Actions, we put in comments on the source code to include such info as description, tag, etc. If we needed to declare the version we are trying to push into Nerdio on a given Intune Policy, perhaps a similar comment based syntax could be used.

Please sign in to leave a comment.