shota_yamasaki

<blockquote data-line="0" class="code-line">
<ul data-line="0" class="code-line">
<li data-line="0" class="code-line">User API tokens that belong to a specific user</li>
<li data-line="1" class="code-line">Team API tokens that belong to a specific team without being tied to any one user</li>
<li data-line="2" class="code-line">The organization API token that provides administrative access to settings and resources at the organizational level</li>
</ul>
</blockquote>
チームやグループで制御するのが基本
<blockquote data-line="5" class="code-line">
Team tokens are the most commonly used token type for automation workflows because they can be scoped with granular access to projects and workspaces. And since they’re not tied to an individual user, there’s less operational risk when users leave the organization.
</blockquote>
あまり活用できていないせいか、気にしたことがなかった
<blockquote data-line="8" class="code-line">
Previously, HCP Terraform only allowed a single team API token per team.
</blockquote>
<iframe id="zenn-embedded__0c73fe1d13f87" src="https://embed.zenn.studio/card#zenn-embedded__0c73fe1d13f87" data-content="https%3A%2F%2Fwww.hashicorp.com%2Fen%2Fblog%2Fterraform-now-supports-multiple-team-tokens" frameborder="0" scrolling="no" loading="lazy"></iframe><a href="https://www.hashicorp.com/en/blog/terraform-now-supports-multiple-team-tokens" style="display:none" target="_blank" rel="nofollow noopener noreferrer">https://www.hashicorp.com/en/blog/terraform-now-supports-multiple-team-tokens</a>