Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
Lab-Terraform
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
LSDS
Teaching
Bachelor
Cloud-and-Deployment
Lab-Terraform
Commits
92365ea7
Commit
92365ea7
authored
3 years ago
by
marcoemi.poleggi
Browse files
Options
Downloads
Patches
Plain Diff
README: fixes. Crypt: added OpenStack/outputs
parent
c8f35b43
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
.gitattributes
+1
-0
1 addition, 0 deletions
.gitattributes
README.md
+5
-7
5 additions, 7 deletions
README.md
with
6 additions
and
7 deletions
.gitattributes
+
1
−
0
View file @
92365ea7
AWS/main.tf.advnc filter=git-crypt diff=git-crypt
AWS/main.tf.advnc filter=git-crypt diff=git-crypt
OpenStack/main.tf.advnc filter=git-crypt diff=git-crypt
OpenStack/main.tf.advnc filter=git-crypt diff=git-crypt
OpenStack/outputs.tf filter=git-crypt diff=git-crypt
This diff is collapsed.
Click to expand it.
README.md
+
5
−
7
View file @
92365ea7
#
# Lab: Cloud provisioning/orchestration - Terraform and AWS
# Lab: Cloud provisioning/orchestration - Terraform and AWS
Lab with Terraform and any Cloud
Lab with Terraform and any Cloud
...
@@ -297,12 +297,10 @@ From the above commands' output we see that
...
@@ -297,12 +297,10 @@ From the above commands' output we see that
*
no changes are applied, and
*
no changes are applied, and
*
huh?... the resource is still stopped.
*
huh?... the resource is still stopped.
Concerning the last point above, think about the basic objectives of TF: as a
:bulb: Concerning the last point above, there is acutally no way with TF to
provisioning tool it is concerned with the
*existence*
of a resource, not with
specify an AWS instances's desired
*runtime*
state (
[
a bug is
its
*runtime*
state. This latter is the business of configuration management
filed
](
https://github.com/hashicorp/terraform-provider-aws/issues/22
)
). Of
tools. :bulb: There is no way with TF to specify a resource's desired runtime
course, this issue can be solved with a configuration management tool.
state.
### Task #4: change your infrastructure ###
### Task #4: change your infrastructure ###
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment