Blog post of the powershell lab #1552
Conversation
✅ Deploy Preview for okta-blog ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
| --- | ||
| layout: blog_post | ||
| title: "Oktane Lab: Scaling Okta App Management by Importing Data from PowerShell into Terraform" | ||
| author: E. Dunham |
There was a problem hiding this comment.
This is the author property, not written name. So it should be something like alisa-duncan and it links to my author profile.
Might want to double check locally
| @@ -0,0 +1,362 @@ | |||
| --- | |||
| layout: blog_post | |||
| title: "Oktane Lab: Scaling Okta App Management by Importing Data from PowerShell into Terraform" | |||
There was a problem hiding this comment.
Out of curiousity, do you need "Oktane Lab" in there? According to the headline analyzer I use, it's much too long at 75 characters
Your headline is much too long. At this length, it will get cut off in search results. Try reducing it to about 55 characters.
It also scores a 31, which is pretty low (I shoot for closer to 70). Removing "Oktane Lab:" gets it in the correct wordcount and a score of 37.
| type: awareness | ||
| --- | ||
|
|
||
| At Oktane 2024, we offered a lab session to teach the basics of automating Okta administration tasks with Terraform and PowerShell. This blog post will walk you through the content taught in that lab so you can follow along at your own pace to get some hands-on experience managing an Okta tenant with both tools. |
There was a problem hiding this comment.
| At Oktane 2024, we offered a lab session to teach the basics of automating Okta administration tasks with Terraform and PowerShell. This blog post will walk you through the content taught in that lab so you can follow along at your own pace to get some hands-on experience managing an Okta tenant with both tools. | |
| At Oktane 2024, we offered a lab session to teach the basics of automating Okta administration tasks with Terraform and PowerShell. This post walks you through the lab content so you can follow along at your own pace to get some hands-on experience managing an Okta tenant with both tools. |
Active and I feel like we prefer "post" instead of "blog" or "blog post" based on my past review notes
|
|
||
| When an identity administrator gives a person the ability to make changes in Okta, they provision the person with credentials to authenticate and scopes to indicate what they're authorized to do. When you set up an automation tool in your Okta organization, it's similar to onboarding any other colleague: Your tool will need credentials to authenticate and scopes to indicate what it's authorized to do. | ||
|
|
||
| ## Scenario |
There was a problem hiding this comment.
Just my 2cents
This might be a candidate for calling out a section in a quote note.
> **Scenario**
>
> You are on the DevOps team at Okta Ice....
|
|
||
| Terraform is a specialized tool for developing infrastructure as code. Terraform requires more setup steps than PowerShell, but adding Okta management to an existing Terraform deployment is more straightforward than designing a new solution with PowerShell. | ||
|
|
||
| ## How to create your lab environment |
There was a problem hiding this comment.
Can we state which versions of Terraform and Okta PowerShell to use (or state which versions you used when testing this lab)? We should pin versions as much as we can
|
|
||
| Note that Terraform creates a `.tfstate` file. Each real-world resource should only be represented in one `.tfstate` file. If you're collaborating on a Terraform codebase, products like [Terraform Cloud](https://www.hashicorp.com/resources/what-is-terraform-cloud) are available to help you manage shared access to `.tfstate` files. | ||
|
|
||
| You will save a private key alongside your code to simplify the lab. In production, you should store keys in your organization's secrets management solution. Because private keys are secrets, follow your organization's best practices for secrets management when dealing with them. |
There was a problem hiding this comment.
| You will save a private key alongside your code to simplify the lab. In production, you should store keys in your organization's secrets management solution. Because private keys are secrets, follow your organization's best practices for secrets management when dealing with them. | |
| You'll save a private key alongside your code to simplify the lab. In production, you should store keys in your organization's secrets management solution. Because private keys are secrets, follow your organization's best practices for secrets management when dealing with them. |
use contractions as listed in our style guide
|
|
||
| To use Terraform, you'll run commands in a terminal. You can even use a PowerShell window if you don't have a favorite terminal! | ||
|
|
||
| If this is your first time writing code, you might want to install an IDE like [Visual Studio](https://code.visualstudio.com/docs/introvideos/basics) so that you can navigate the files you're writing, detect errors using plugins, and execute commands using the built-in terminal. |
There was a problem hiding this comment.
Should IDE be defined for this audience?
| ``` | ||
| terraform init | ||
| terraform plan | ||
| ``` |
There was a problem hiding this comment.
I think you're missing a newline or something. the syntax highlighting in GH is catching a problem here
| 8. Authenticate to your Okta Training Org when prompted. | ||
| 9. In your PowerShell session, run the command `Invoke-OktaListApplications` | ||
|
|
||
| ## Extra Credit |
There was a problem hiding this comment.
headers should be sentence case.
|
|
||
| ## Manage Terraform in Terraform | ||
|
|
||
| 1) In your PowerShell session from the previous section, run the command `powershell Invoke-OktaListApplications` |
There was a problem hiding this comment.
Why did this numbering system change to parens instead of a dot?
| --- | ||
| layout: blog_post | ||
| title: "Oktane Lab: Scaling Okta App Management by Importing Data from PowerShell into Terraform" | ||
| author: E. Dunham |
| - Install [PowerShell](https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell?view=powershell-7.4). | ||
| - Install the [official Okta PowerShell module](https://github.com/okta/okta-powershell-cli) from your preferred PowerShell module location. | ||
| - Install [Terraform](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli). | ||
| - Create an Okta org by [signing up](/signup/) for Workforce Identity Cloud. |
There was a problem hiding this comment.
link to okta org creation not working
|
|
||
| When an identity administrator gives a person the ability to make changes in Okta, they provision the person with credentials to authenticate and scopes to indicate what they're authorized to do. When you set up an automation tool in your Okta organization, it's similar to onboarding any other colleague: Your tool will need credentials to authenticate and scopes to indicate what it's authorized to do. | ||
|
|
||
| ## Scenario |
There was a problem hiding this comment.
Enterprise scenario 1? For SEO on headers
|
|
||
| If you aren't using PowerShell, you can get the Terraform integration ID from the Okta admin console instead. | ||
|
|
||
| ## Scenario |
| } | ||
| ``` | ||
|
|
||
| ## Conclusion |
There was a problem hiding this comment.
Continue learning more about PowerShell and Terraform -- suggestion for SEO
This blog post has the following features: