Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot open policy in GUI policy editor #244585

Closed
jrieken opened this issue Mar 25, 2025 · 5 comments
Closed

Cannot open policy in GUI policy editor #244585

jrieken opened this issue Mar 25, 2025 · 5 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone

Comments

@jrieken
Copy link
Member

jrieken commented Mar 25, 2025

Testing #244530

Don't really know what I am doing here, the TPI is vague, but this is what I see when I open the policy in the suggested GUI app

Screenshot 2025-03-25 at 13 24 53
@joshspicer
Copy link
Member

joshspicer commented Mar 25, 2025

Thanks for testing - I want to double check you saw the vnext docs that I linked to?

This plist file is the one you'd provide to iMazing (iMazing will ultimately generate a mobileconfig file, saving you from needing to manually edit the one i provide)

Image

@jrieken
Copy link
Member Author

jrieken commented Mar 26, 2025

Maybe the docs should make that more obvious, unless everyone involved in policy works just knows this things

@joaomoreno
Copy link
Member

joaomoreno commented Mar 26, 2025

I also got confused, got into the same rat hole. Unsure if we should link to that app from our docs. Usually sysadmins know what they are doing.

The tool doesn't even allow me to open the plist by default

Image

@joaomoreno joaomoreno added the under-discussion Issue is under discussion for relevance, priority, approach label Mar 26, 2025
@joshspicer
Copy link
Member

Thanks for the feedback. I was inspired to include it from other product docs, like tailscale's

It is a nicer experience for products that check in their plists to their repo, but we probably don't want that maintenance overhead (at least until the number of policies stabilizes a bit)

I'm OK removing it from the docs and leaving it up to sysadmins familiar with the space to utilize if they'd like.

@joshspicer joshspicer added this to the March 2025 milestone Mar 26, 2025
@joshspicer joshspicer added the bug Issue identified by VS Code Team member as probable bug label Mar 26, 2025
@amunger amunger modified the milestones: March 2025, April 2025 Mar 28, 2025
@joshspicer
Copy link
Member

removed reference to this editor in the docs

@joshspicer joshspicer modified the milestones: April 2025, March 2025 Apr 1, 2025
@rzhao271 rzhao271 added verified Verification succeeded and removed under-discussion Issue is under discussion for relevance, priority, approach labels Apr 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

5 participants