Release kiota image on mcr.microsoft.com and dotnet tool on nuget.org

[PureKrome]

Can we please have the docker image stored in the newer ghcr.io registry? means we don't need auth/PAT's.

Currently there are 2 GH Docker registries, one at docker.pkg.github.com and a new one at ghcr.io. The original registry always requires a PAT with the read:packages scope (even for public packages). The new ghcr.io registry has the option to create true public container packages.

If you publish an image to ghcr.io you can make it public with no auth required. See here for more information:
https://docs.github.com/en/packages/guides/configuring-access-control-and-visibility-for-container-images#configuring-visibility-of-container-images-for-an-organization
AB#9098

[baywet]

Hey @PureKrome,
Thanks for the feedback. I do not have permissions to change that setting on an organization level. I've asked around though and we'll see if this can get changed.
I suspect I'll get a negative answer as all official Microsoft images should be on mcr.microsoft.com. We're planning to publish the container image there once we go to beta so people don't have to login anymore and it's easier to discover through the docker hub.

[PureKrome]

I suspect I'll get a negative answer as all official Microsoft images should be on mcr.microsoft.com.

That's totally kewl -> wasn't suggesting for the final production one(s) ... just the "in development" ones. But yeah, forgot that this was an ORG setting ... which .. hopefully ... the people in charge will understand and see the logical benefit of using ghcr.io for these beta/test images, instead of the older docker.pkg.github.com for these beta/test images.

[baywet]

I got a reply, as a suspected this setting won't be turned on due to internal policies. If we want to publish this container publicly, we need to publish it on mcr.microsoft.com. Granted mcr.microsoft.com/dotnet/aspnet:6.0 is there, my guess is it's ok to publish preview containers there as well.
The onboarding instructions are here (you won't be able to access it, that's for me later).

Let me check our plans with @darrelmiller and come back to you on this one.

[baywet]

We're out of out planning session. Here is an update: we'll leave it like that for now as it allows us to experiment things and avoid having too much exposure. The generator needs some work before it's ready for a "prime preview time" as you can see with #127 And I'm sure you as well as other super-early adopters will provide crucial feedback too.

The generator should go out publicly in preview (no more sign-in, on MCR) whenever the abstractions packages are publicly available as well as it makes no sense to unlock the generator but then require sign in when people use the packages. (see #128)

[PureKrome]

great! i'll give it a go with the PAT, etc.

[baywet]

We'll keep your issue open to track the work :)

[PureKrome]