sshockley

It looks like someone at Red Hat is doing something for 7.7, but I can't view most of the bugs: https://bugzilla.redhat.com/buglist.cgi?bug_id=1673905&bug_id_type=andblocked&format=tvp&tvp_dir=blocked (expand all)

The ln command is backwards; this worked for me: ```sudo ln -s /usr/lib/x86_64-linux-gnu/libfuzzy.so /usr/local/lib/libfuzzy.so``` I also had to install libfuzzy2 manually (via apt). A better solution might be to update...

This PR doesn't include the files created by the workflow, since that would make it more difficult to review. I did have to manually create the subfolders as the script...

Thanks, sorry I was unresponsive. We wound up switching over to Enterprise-Scale for now, will re-eval once US Gov is added, that's a bigger job than I first thought. Thanks!

Semi-related, it looks like the USGovernment policy versions are different? I kind of expected that, but I didn't exped USGovernment to have a higher version. Commercial policy (8.2.0): https://github.com/Azure/azure-policy/blob/master/built-in-policies/policyDefinitions/Kubernetes/IngressHttpsOnly.json USGovernment...

I found a couple. I'll create a PR shortly.

Thanks for the info. In general, I've been able to deploy by passing "" as topLevelManagementGroupPrefix, but maybe I've just been lucky. I do realize that ideally I shouldn't shoehorn...

I created a PR in what seems to be the upstream repo. Hopefully someone takes a look at it, but based on the other PRs in that repo it looks...

I now see this is probably related to #539 as well, which has a pending PR.

@fergusstrachan, maybe try running winget upgrade --all from an elevated command prompt and see if winget without WAU will do the upgrade. I have had some problems with winget when...