+1 (nb)
Verified signature, checksum.
JB: I believe you mentioned in the community sync call that you were going
to share some info on how releases are supposed to be verified :)
Cheers,
Dmitri.
On Wed, Jan 8, 2025 at 11:01 AM Jean-Baptiste Onofré
wrote:
> Hi folks,
>
> As mentioned in anothe
While I think more tests that mocked or emulated storage would be great, I
think we probably want tests hitting "real" storage in addition to those.
I would be in favor of running the "real" storage tests less often. For
example, only prior to merging or to cutting a release.
--EM
On Fri, Jan 10
Hi All,
I see that some tests (e.g. for GCP and Azure) apparently require special
settings to be able to run.
Would there be any objections to gradually converting those tests to use
emulators or containerized storage (like MinIO) and hence have no special
settings or secrets?
Thanks,
Dmitri.
I believe tests against real storage systems are highly valuable,
especially since Polaris relies entirely on three distinct cloud storage
providers at this moment, each with its own quirks and unique features.
These tests help ensure robustness and compatibility across these platforms.
To balance
+1(non-binding)
Verified signature, checksum. Build passed.
Yufei
On Fri, Jan 10, 2025 at 3:45 PM Dmitri Bourlatchkov
wrote:
> +1 (nb)
>
> Verified signature, checksum.
>
> JB: I believe you mentioned in the community sync call that you were going
> to share some info on how releases are supp
Hi Dmitri
That's right: https://github.com/apache/polaris/issues/648
I will open a PR soon.
Regards
JB
On Sat, Jan 11, 2025 at 12:44 AM Dmitri Bourlatchkov wrote:
>
> +1 (nb)
>
> Verified signature, checksum.
>
> JB: I believe you mentioned in the community sync call that you were going
> to s
Thanks!
There's a "Dependency Dashboard" that gives an overview of the state of
all the dependencies. Please do not close this issue
https://github.com/apache/polaris/issues/642.
Please do not trigger the "Config Migration PR", because that would
effectively remove the (hopefully useful) com
Real storage implies real credentials, which will necessarily restrict OSS
users.
For example, outside contributors will have no ability to run (and debug)
the full set of tests.
My previous experience in OSS projects that had a private CI component is
that this model does not scale well in terms
Hi folks,
I guess you saw new PRs created by renovate.
I finally found a way to enable renovate on the Apache Polaris repo
(read-only), and the configuration has now moved to
.github/renovate.json5.
Regards
JB
