From 92365ea734221bfc90eb5f91c9d2ad21766cc734 Mon Sep 17 00:00:00 2001
From: Marco Emilio Poleggi <marco-emilio.poleggi@hesge.ch>
Date: Wed, 9 Feb 2022 09:58:14 +0100
Subject: [PATCH] README: fixes. Crypt: added OpenStack/outputs

---
 .gitattributes |  1 +
 README.md      | 12 +++++-------
 2 files changed, 6 insertions(+), 7 deletions(-)

diff --git a/.gitattributes b/.gitattributes
index 87cdcf4..6c728f4 100644
--- a/.gitattributes
+++ b/.gitattributes
@@ -1,2 +1,3 @@
 AWS/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
diff --git a/README.md b/README.md
index 015af97..54704ea 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,4 @@
-## Lab: Cloud provisioning/orchestration - Terraform and AWS
+# Lab: Cloud provisioning/orchestration - Terraform and AWS
 
 Lab with Terraform and any Cloud
 
@@ -297,12 +297,10 @@ From the above commands' output we see that
   * no changes are applied, and
   * huh?... the resource is still stopped.
 
-Concerning the last point above, think about the basic objectives of TF: as a
-provisioning tool it is concerned with the *existence* of a resource, not with
-its *runtime* state. This latter is the business of configuration management
-tools. :bulb: There is no way with TF to specify a resource's desired runtime
-state.
-
+:bulb: Concerning the last point above, there is acutally no way with TF to
+specify an AWS instances's desired *runtime* state ([a bug is
+filed](https://github.com/hashicorp/terraform-provider-aws/issues/22)). Of
+course, this issue can be solved with a configuration management tool.
 
 ### Task #4: change your infrastructure ###
 
-- 
GitLab