<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Feature Request: API support for Context-Based Ingress Control IP lists in Administration &amp; Architecture</title>
    <link>https://community.databricks.com/t5/administration-architecture/feature-request-api-support-for-context-based-ingress-control-ip/m-p/155608#M5194</link>
    <description>&lt;P&gt;I know that &lt;A href="https://docs.databricks.com/gcp/en/security/network/front-end/context-based-ingress" target="_self"&gt;context-based ingress control&lt;/A&gt; is currently a preview feature, but it is an extremely important one. It removes the need for workspace-level IP access lists, making it much easier to govern allowed IPs centrally and preventing workspace-level admins from modifying them.&lt;/P&gt;&lt;P&gt;For an organization, this context-based approach makes much more sense. However, without an API to update the IPs programmatically, it is difficult to maintain access lists for dynamic ranges like Google public IPs and other services.&lt;/P&gt;&lt;P&gt;I would just like to know if an API for this is on the roadmap, and if my understanding of the context-based ingress control's scope is correct.&lt;/P&gt;</description>
    <pubDate>Mon, 27 Apr 2026 17:26:59 GMT</pubDate>
    <dc:creator>ismaelhenzel</dc:creator>
    <dc:date>2026-04-27T17:26:59Z</dc:date>
    <item>
      <title>Feature Request: API support for Context-Based Ingress Control IP lists</title>
      <link>https://community.databricks.com/t5/administration-architecture/feature-request-api-support-for-context-based-ingress-control-ip/m-p/155608#M5194</link>
      <description>&lt;P&gt;I know that &lt;A href="https://docs.databricks.com/gcp/en/security/network/front-end/context-based-ingress" target="_self"&gt;context-based ingress control&lt;/A&gt; is currently a preview feature, but it is an extremely important one. It removes the need for workspace-level IP access lists, making it much easier to govern allowed IPs centrally and preventing workspace-level admins from modifying them.&lt;/P&gt;&lt;P&gt;For an organization, this context-based approach makes much more sense. However, without an API to update the IPs programmatically, it is difficult to maintain access lists for dynamic ranges like Google public IPs and other services.&lt;/P&gt;&lt;P&gt;I would just like to know if an API for this is on the roadmap, and if my understanding of the context-based ingress control's scope is correct.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2026 17:26:59 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/feature-request-api-support-for-context-based-ingress-control-ip/m-p/155608#M5194</guid>
      <dc:creator>ismaelhenzel</dc:creator>
      <dc:date>2026-04-27T17:26:59Z</dc:date>
    </item>
  </channel>
</rss>

