add terraform quickstart blog#24
Conversation
|
@jorgemoralespou please review current draft. note the terraform apply asciinema needs a re-record - encountered a failure on initial kapp controller deployment, see educates/educates-terraform-modules#14 |
jorgemoralespou
left a comment
jorgemoralespou
left a comment
There was a problem hiding this comment.
Thanks, it's good, although I would make more emphasis, as stated in my comments to the fact that, what we support and release are the individual modules, and that what's in root_modules is a inspirational implementation.
| 7. **Educates CLI**: | ||
| We'll need to deploy/manage a workshop to verify the cluster by either method: | ||
| - Download the [Educates CLI directly](https://github.com/educates/educates-training-platform/releases/tag/3.3.2), | ||
| - Use the [Educatesenv tool to manage the installation of Educates](../blog/managing-multiple-versions-of-educates-cli). |
There was a problem hiding this comment.
Make this a global link, so /blog/managing-multiple-versions-of-educates-cli
| If you prefer to install Educates via the CLI as in [Installing Educates on a cloud provider article](../blog/install-educates-cloud-cli), | ||
| set the `deploy_educates` flag to `false`. | ||
| The Educates module will not be deployed. | ||
|
|
There was a problem hiding this comment.
Add a note that, while this modules are a convenience or reference implementation, what we're really releasing are the independent modules that can be consumed in your own custom terraform plans. In that case, one should use the whole tag version of the module, like this:
source = "github.com/educates/educates-terraform-modules.git//infrastructure/gke-for-educates?ref=v1.0.2"
And that these are the modules that are really released and versioned, and the changes are documented in the release page at https://github.com/educates/educates-terraform-modules/releases
There was a problem hiding this comment.
@jorgemoralespou see latest commit updates, main theme is to expand and differentiate about infrastructure, platform and root modules.
|
|
||
| State of the terraform plan and the associated cluster deployment workflow is not automatically saved elsewhere, | ||
| so if you were to modify or delete these resources, | ||
| you would not be able to update or destroy your cluster using Terraform. |
There was a problem hiding this comment.
I would add:
This is one of the reasons these are just example reference implementations, and it's up to you to know what you're doing. You should use the released modules in your own plans, taking inspiration from these reference implementations, but guaranteeing to properly save the state of your plan executions.
Or something the likes
There was a problem hiding this comment.
@jorgemoralespou this section is also added in latest.
|
@jorgemoralespou the terraform-apply.cast is fixed too. |
billkable
force-pushed
the
add-terraform-quickstart-blog
branch
from
4d63921 to
b8a360d
Compare
2 participants
Initial draft of public terraform modules release announcement and quick start.