From a0cbc9967c6acfe1b68ead1a1d9135f62ee65ba8 Mon Sep 17 00:00:00 2001 From: Ric Harvey Date: Tue, 16 Apr 2024 19:29:52 +0100 Subject: [PATCH] adding url for gitlab state storage --- 3-remote-states/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/3-remote-states/README.md b/3-remote-states/README.md index 92bab66..fb2ed0e 100644 --- a/3-remote-states/README.md +++ b/3-remote-states/README.md @@ -193,7 +193,7 @@ Now you'll notice theres no longer a ```terraform.state``` file clogging up you You won't see much in dynamoDB unless you are currently in the middle of an **apply** but that value of ```LockID``` gets set when you are updating or deploying the stack to avoid others overwriting the file in S3. -Thats it you're done! You now have remote state configued for use on AWS using DynamoDB and S3, this means more than just you can operate your stack deployed by terraform/tofu which is essential for teams. If you want to lookinto other ways of storing state check out the documentation here: [https://opentofu.org/docs/language/state/remote-state-data/](https://opentofu.org/docs/language/state/remote-state-data/) +Thats it you're done! You now have remote state configued for use on AWS using DynamoDB and S3, this means more than just you can operate your stack deployed by terraform/tofu which is essential for teams. If you want to lookinto other ways of storing state check out the documentation here: [https://opentofu.org/docs/language/state/remote-state-data/](https://opentofu.org/docs/language/state/remote-state-data/) you can also check out how to store state in Gitlab here: [https://docs.gitlab.com/ee/user/infrastructure/iac/terraform_state.html](https://docs.gitlab.com/ee/user/infrastructure/iac/terraform_state.html) ### Clean up