Hi JB - coming back from vacation and picking this back up :)

I tried using ASF self-serve portal and ran into some issues. There's an open 
GH issue for this: https://github.com/apache/infrastructure-boxer/pull/47

Is there a different approach?

The ASF Infra ticket is unfortunately still pending as well, so I'd appreciate 
any pointers on getting this unblocked.

Sung


On 2026/07/20 05:04:28 Jean-Baptiste Onofré wrote:
> Hi
> 
> We didn't need an infra ticket: we can create the repository
> ourselves, including if the name is not "conventional".
> 
> I will tackle the infra ticket directly :)
> 
> Regards
> JB
> 
> 
> On Fri, Jul 17, 2026 at 5:23 PM Sung Yun <[email protected]> wrote:
> >
> > Thanks, everyone. As 72 hours have now passed without objection, I'll move 
> > forward with creating the repository.
> >
> > I've opened an Apache INFRA JIRA to request repository creation, as the 
> > unconventional repository name is not yet supported by the self-service 
> > portal.
> >
> > I'll update this thread once the repository is successfully created.
> >
> > Sung
> >
> >
> > On 2026/07/14 01:16:14 Yong Zheng wrote:
> > > +1
> > >
> > > Thanks,
> > > Yong Zheng
> > >
> > > > On Jul 13, 2026, at 7:19 PM, Dmitri Bourlatchkov <[email protected]> 
> > > > wrote:
> > > >
> > > > Hi Sung,
> > > >
> > > > Thanks for volunteering! I agree that it is fine to go ahead with this
> > > > repository creation in 72 hours.
> > > >
> > > > Cheers,
> > > > Dmitri.
> > > >
> > > >> On Mon, Jul 13, 2026 at 8:16 PM Sung Yun <[email protected]> wrote:
> > > >>
> > > >> Hi folks,
> > > >>
> > > >> It looks like we are generally in agreement that this is a good idea.
> > > >> Given that the HashiCorp Cloud Platform Public Registry has a 
> > > >> restriction
> > > >> on the repository name, creating the repository as
> > > >> "terraform-provider-polaris" sounds reasonable.
> > > >>
> > > >> If there are no objections to creating this repository under that name 
> > > >> in
> > > >> the next 72 hours, I will see that as lazy consensus, and go ahead and 
> > > >> set
> > > >> up the repository.
> > > >>
> > > >> Thanks,
> > > >> Sung
> > > >>
> > > >>> On 2026/07/07 19:52:02 Alex Stephen via dev wrote:
> > > >>> It will need a dedicated repository that must be
> > > >>> called `terraform-provider-polaris`. The Terraform Registry (their
> > > >> package
> > > >>> manager) is very opinionated about repository names
> > > >>> <https://developer.hashicorp.com/terraform/registry/providers/publishing
> > > >>> .
> > > >>>
> > > >>> On Tue, Jul 7, 2026 at 7:59 AM Jean-Baptiste Onofré 
> > > >>> <[email protected]>
> > > >> wrote:
> > > >>>
> > > >>>> Hi Alex
> > > >>>>
> > > >>>> That looks great to me.
> > > >>>>
> > > >>>> Does it need a separate/dedicated repository or can it be part of the
> > > >>>> polaris-tools repo?
> > > >>>>
> > > >>>> Regards
> > > >>>> JB
> > > >>>>
> > > >>>> On Mon, Jul 6, 2026 at 8:21 PM Alex Stephen via dev <
> > > >>>> [email protected]> wrote:
> > > >>>>
> > > >>>>> Hello,
> > > >>>>>
> > > >>>>> The Apache Iceberg project has been working on a Terraform Provider
> > > >>>>> <https://github.com/apache/terraform-provider-iceberg>. We're hoping
> > > >> to
> > > >>>>> release it soon. We originally accepted some PRs for Polaris-based
> > > >>>>> resources (Polaris Principals mainly), but the community decided we
> > > >> should
> > > >>>>> focus exclusively on Iceberg resources.
> > > >>>>>
> > > >>>>> We'd like to rehome the Polaris resources into a dedicated Polaris
> > > >>>>> Terraform Provider. I'm more than happy to dedicate time to making
> > > >> this
> > > >>>>> happen. It would need to live in a dedicated repository called
> > > >>>>> "terraform-provider-polaris," since the Terraform Registry is
> > > >>>>> opinionated about that.
> > > >>>>>
> > > >>>>> Is this something the community is interested in?
> > > >>>>>
> > > >>>>> Thanks!
> > > >>>>>
> > > >>>>> -- Alex Stephen
> > > >>>>>
> > > >>>>
> > > >>>
> > > >>
> > >
> 

Reply via email to