new blog post about Terraform V1.0 release #1206
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TeganAli
reviewed
Apr 17, 2025
|
|
||
| ## Clearer documentation with practical examples | ||
|
|
||
| For a better user experience, we updated our documentation to include detailed examples and best practices for using the Terraform Provider effectively. We outlined 5 key scenarios to guide you. The documentation found at [the Terraform registry](https://registry.terraform.io/providers/OctopusDeployLabs/octopusdeploy/latest/docs) now also has examples for all data sources and resources. |
There was a problem hiding this comment.
@Vvasudevan-octopus where it says "we updated our documentation" we should provide a link to the docs.
TeganAli
reviewed
Apr 17, 2025
|
|
||
| We resolved several long-standing bugs in this release. This improves the provider and ensures a more stable and reliable experience. | ||
|
|
||
| - New deployment process resource: We made it easier to define and manage deployment processes by making each step its own resource. We also introduced a step order resource so you can easily manage the deployment process step order. You can find out more info on how it works in the official docs. |
There was a problem hiding this comment.
@Vvasudevan-octopus where it says "in the official docs" we should provide a link to the docs.
TeganAli
reviewed
Apr 17, 2025
|
|
||
| ### Provider migrated to Octopus Deploy repository | ||
|
|
||
| The Terraform provider has always lived in our OctopusDeployLabs repository, which signalled that it was an experimental integration. We decided to move it to our official repository, elevating it as a core integration. |
There was a problem hiding this comment.
@Vvasudevan-octopus where it says "our official repository" we should provide a link to the repo.
TeganAli
reviewed
Apr 17, 2025
|
|
||
| The v1.0 release solidifies the Octopus Deploy Terraform provider as a robust tool for managing your Octopus instance as code. By simplifying resource management and improving documentation, teams can work more efficiently with the Terraform provider | ||
|
|
||
| For detailed information on all changes and enhancements, please read the docs or visit the Terraform registry page for the provider. |
There was a problem hiding this comment.
@Vvasudevan-octopus where it says "read the docs" we should provide a link to the docs, and where it says "visit the Terraform registry page for the provider" we should also provide a link.
I've added the following - Added links where they were previously missing - Removed the Octo-terra tool paragraph as we are no longer doing this
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
About
This is a post about the V1.0 release of the Terraform provider
Release
No, this is for an integration with octopus
Blog image idea
Image is already attached
Before you submit your post
Check everything off this list before you submit your post for review.
How to review this PR
Apologies if I've made any basic errors, this is my first time submitting a blog post!
Publication date
This post should not be published until I send confirmation that we have released V1.0 around the end of April / 1st week of May