<?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 Re: Terraforming Git credentials for service principals in Administration &amp; Architecture</title>
    <link>https://community.databricks.com/t5/administration-architecture/terraforming-git-credentials-for-service-principals/m-p/120357#M3398</link>
    <description>&lt;P&gt;You're a little bit ahead of me in this process, so I haven't tried the solution yet, but it looks like you create a git credential resource for the service principal.&amp;nbsp; This requires a token, which I think must be generated in the console.&amp;nbsp; My reference is&amp;nbsp;&lt;A href="https://learn.microsoft.com/en-us/azure/databricks/repos/automate-with-terraform" target="_blank"&gt;Terraform integration - Azure Databricks | Microsoft Learn&lt;/A&gt;.&lt;/P&gt;</description>
    <pubDate>Tue, 27 May 2025 18:07:11 GMT</pubDate>
    <dc:creator>Rjdudley</dc:creator>
    <dc:date>2025-05-27T18:07:11Z</dc:date>
    <item>
      <title>Terraforming Git credentials for service principals</title>
      <link>https://community.databricks.com/t5/administration-architecture/terraforming-git-credentials-for-service-principals/m-p/120011#M3394</link>
      <description>&lt;P&gt;I am terraforming service principals in my Databricks workspace and it works great until I need to assign Git credentials to my SP. In the UI we have these options to configure credentials on service principal page:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="vr_0-1747957962260.png" style="width: 400px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/17066i02EA4AB7D2A0513B/image-size/medium?v=v2&amp;amp;px=400" role="button" title="vr_0-1747957962260.png" alt="vr_0-1747957962260.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P data-unlink="true"&gt;However the &lt;A href="https://registry.terraform.io/providers/databricks/databricks/latest/docs/resources/git_credential" target="_blank" rel="noopener"&gt;Terraform resource&lt;/A&gt; I found seems to lack the critical piece – &lt;EM&gt;which service principal&lt;/EM&gt; these credentials are for. Also &lt;A href="https://docs.databricks.com/api/workspace/gitcredentials" target="_blank" rel="noopener"&gt;the API&lt;/A&gt; it references&amp;nbsp;&lt;A href="https://docs.databricks.com/api/azure/workspace/gitcredentials/create" target="_blank" rel="noopener"&gt;says&lt;/A&gt;&amp;nbsp;that it sets the credentials for the &lt;STRONG&gt;calling user&lt;/STRONG&gt;. So, I need to call this API on behalf of the created service principal? Weird. This is not how IaC should work.&lt;/P&gt;&lt;P data-unlink="true"&gt;So... It looks like these capability is fundamentally missing in Databricks API? I cannot even create a feature request in Terraform project, because there is nothing to request. Is my understanding correct?&lt;/P&gt;&lt;P data-unlink="true"&gt;Databricks, why is there no parity between UI and API?&lt;/P&gt;</description>
      <pubDate>Fri, 23 May 2025 00:07:02 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/terraforming-git-credentials-for-service-principals/m-p/120011#M3394</guid>
      <dc:creator>vr</dc:creator>
      <dc:date>2025-05-23T00:07:02Z</dc:date>
    </item>
    <item>
      <title>Re: Terraforming Git credentials for service principals</title>
      <link>https://community.databricks.com/t5/administration-architecture/terraforming-git-credentials-for-service-principals/m-p/120357#M3398</link>
      <description>&lt;P&gt;You're a little bit ahead of me in this process, so I haven't tried the solution yet, but it looks like you create a git credential resource for the service principal.&amp;nbsp; This requires a token, which I think must be generated in the console.&amp;nbsp; My reference is&amp;nbsp;&lt;A href="https://learn.microsoft.com/en-us/azure/databricks/repos/automate-with-terraform" target="_blank"&gt;Terraform integration - Azure Databricks | Microsoft Learn&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Tue, 27 May 2025 18:07:11 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/terraforming-git-credentials-for-service-principals/m-p/120357#M3398</guid>
      <dc:creator>Rjdudley</dc:creator>
      <dc:date>2025-05-27T18:07:11Z</dc:date>
    </item>
    <item>
      <title>Re: Terraforming Git credentials for service principals</title>
      <link>https://community.databricks.com/t5/administration-architecture/terraforming-git-credentials-for-service-principals/m-p/120363#M3400</link>
      <description>&lt;P&gt;So this method seems like defines a whole TF provider to use it as context? Isn't it strange? With infrastructure-as-code, you usually have a single (superuser) identity under which the provider works and which is capable of creating any objects, including other identities.&lt;/P&gt;&lt;P&gt;I expect it to work in this paradigm, because my actual IaC layer is Crossplane, which is Terraform-based, but I don't have all capabilities of Terraform. In particular, a Crossplane equivalent of a provider would be provider configuration, which is defined statically in the cluster. I cannot create a provider configuration "on the fly" (or maybe I don't know how to do that).&lt;/P&gt;</description>
      <pubDate>Tue, 27 May 2025 18:55:40 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/terraforming-git-credentials-for-service-principals/m-p/120363#M3400</guid>
      <dc:creator>rv1</dc:creator>
      <dc:date>2025-05-27T18:55:40Z</dc:date>
    </item>
    <item>
      <title>Re: Terraforming Git credentials for service principals</title>
      <link>https://community.databricks.com/t5/administration-architecture/terraforming-git-credentials-for-service-principals/m-p/120466#M3408</link>
      <description>&lt;P&gt;No, the module created here is for the service principal which needs to be configured, not the context Terraform runs under.&lt;/P&gt;</description>
      <pubDate>Wed, 28 May 2025 19:13:40 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/terraforming-git-credentials-for-service-principals/m-p/120466#M3408</guid>
      <dc:creator>Rjdudley</dc:creator>
      <dc:date>2025-05-28T19:13:40Z</dc:date>
    </item>
    <item>
      <title>Re: Terraforming Git credentials for service principals</title>
      <link>https://community.databricks.com/t5/administration-architecture/terraforming-git-credentials-for-service-principals/m-p/120480#M3409</link>
      <description>&lt;P&gt;Yeah, that's what I mean, thanks for confirming.&lt;/P&gt;&lt;P&gt;I expect, that, if I am able to create the service principal under the main Terraform identity, I should be able to configure its parameters as well (workspace privileges, secrets, Git configuration, etc). So if I need to run Terraform under the identity of the created SP, then what's the point? it's not quite the IaC I need.&lt;/P&gt;</description>
      <pubDate>Wed, 28 May 2025 21:57:48 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/terraforming-git-credentials-for-service-principals/m-p/120480#M3409</guid>
      <dc:creator>vr</dc:creator>
      <dc:date>2025-05-28T21:57:48Z</dc:date>
    </item>
  </channel>
</rss>

