Feature/cf 1190 introduce quote endpoint

[StefosGeo]

Introducing a new endpoint called quote. Users with the write:cluster permission will be able to get the pricing for the cluster included any available discounts.

[github-actions]

PR Packages Published

Python Package:

• Version: 0.59.0.dev208+e67b7c0
• Package: qdrant-cloud-public-api
• Registry: https://us-python.pkg.dev/qdrant-cloud/python/
• To update run: uv add qdrant-cloud-public-api==0.59.0.dev208+e67b7c0

NPM Package:

• Version: 0.59.0-dev208.e67b7c0
• Package: @qdrant/qdrant-cloud-public-api
• Registry: https://us-npm.pkg.dev/qdrant-cloud/npm/
• To update run: npm install @qdrant/[email protected]

[github-actions]

The latest Buf updates on your PR. Results from workflow Pull Request / linting (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	✅ passed	✅ passed	✅ passed	Oct 2, 2025, 1:30 PM

[github-actions]

It looks like the PR doesn't include updates for the generated code.

Please make sure you've run the following commands from the root directory:

make generate

Once you've added them, you can dismiss this review.

[Robert-Stam]

IMO We should have a proper permission, I don't like we leak endpoints which in enterprises should not be able to be called unless allowed.

[lomidzemikheili]

Now the api requires authentication but does not require the permission.

I would go with public api - without authentication and permission. It can be useful for calculator page for example.

or If we want it to be authenticated, then we should add a permission for it.

Since the response may has info about discounts, I would go with authenticated and permission checked api.

[StefosGeo]

how does it sound if I add a read:discounts permission, and if the user has it he will see the discounted price, if not he will see the prices with zero discount

[StefosGeo]

I drafted the following implementation:
• The getquote endpoint will be public in general, but discounts will only be applied if the user has the read:discount permission. Otherwise, the user will see the quote without discounts, even if they exist.

After discussing this with the team, a few concerns were raised:
• Some felt it’s not clean to have different behavior in the same endpoint depending on permissions. An alternative would be to expose two separate endpoints (getquote and getquote_withdiscounts), letting the client decide based on permissions. At the very least, the response should make it explicit whether no discounts exist versus the user not being allowed to see them.
• Others argued that permissions might not be the right tool for this, and that a more fine-grained ABAC approach would be preferable (though we don’t have such a system in place yet).
• It was also mentioned that we could start with no permissions for this at all.

cc @pansen @Rendez
What do you think @Robert-Stam @lomidzemikheili?

[StefosGeo]

New update, we believe that if the user has the write to create cluster he should see the price including any discounts

[lomidzemikheili]

Nice work!

Left two comments

[lomidzemikheili]

Now the api requires authentication but does not require the permission.

I would go with public api - without authentication and permission. It can be useful for calculator page for example.

or If we want it to be authenticated, then we should add a permission for it.

Since the response may has info about discounts, I would go with authenticated and permission checked api.

[github-actions]

It looks like the PR doesn't include updates for the generated code.

Please make sure you've run the following commands from the root directory:

make generate

Once you've added them, you can dismiss this review.

[lomidzemikheili]

Nice!

Thanks for addressing the feedback

make generate