Відео

Can I reference the output of a stack that's in a different space using terraform remote state or is that only possible with dependencies? Like if I have a global space that needs to reference a vpc output from my prod space.

This is great!

Thanks. This is a great primer for Terraform state and lock files.

startups should be able to defend themselves from subsidizing big tech

thanx

from where i can get repo u showed

Great video and amazing explanation.

Can I used same terraform state file to create resources in different regions. Pl answer Thanks in advance. 🙏

Can make an short what is this licence and stuff

why can't a tool like terraform check what resources are available in the Cloud by connecting with the Cloud instance in question? Why keep a record of reality when you could in principle examine the real thing?

As someone who love eating Tofu, I love the name 😁

Hi, I didn't find anything about how to migrate TFC's Registry module, I try to migrate one with module to Spacelift but it run error with missing module even I import the same module to Spacelift Terraform registry

That looks neat!

Well done, great explanation

How would someone new to all this learn to use open tofu? Best to just learn terraform for now?

too fast

this is truly awesome

Hello nice information need more videos!

terraform has changed their provider licence, you cant use terraform providers with anything other than terraform. i just tried opentofu and i cant seem to run tofu init since it requires a terraform provider to deploy my stack. is there a work around for this? or are we stuck using terraform again?

OpnToFu is a terrible name. Don't eat the soy guys, eat grass fed beef ;) .

I followed your example, but my stack inside space lift will not run when I push new code to the repository. It seems to be stuck on the commit that was used to create the stack. When doing some research, it looks like there is a way to sync it using the button, but there is no button available, did I miss a step somewhere in order to get the stack to run on every commit?

Why can't the lock file also be created in the S3 bucket? Not fast enough?

The lack of reaction from Hashicorp on the request to change their license back would, at least on the surface, seem to the be start of the end of Terraform. All the utilities that use the libraries from Hashicorp (tfenv, terraform-docs, tflint, pre-commit handler for Terraform are 4 that come to mind) are now going to also need upgrading in some fashion. I wish Hashicorp could have shared the information that they would seem to have about who is actually/currently incorporating Terraform into competitive products (otherwise why waste the time and effort to make this change if there is no benefit). The sad thing is, but doing this licence change ... AND the fork now existing ... those competitive products can now be further developed unrestricted (I think) and so would seem further defines the start of the end of Terraform.

lol, I am already appearing for TF 🤦‍♂

It will be „forever” open source, who will guarantee that?

Excellent tool. Let's see how this progresses towards Open Tofu (or the other way around 😀)

I'm guessing videos like this made hashi decide to go to bsl.

Really glad to see it!

#Question: won't hashicorp sue OpenTF as they forked their codebase? and will use it? or it can't because it was opensource, but now it is not anymore so it can sue technically, right? please describe.

Hashicorp be like: "I changed the contract, pray I don't change it further"

Thanks for making my day 3 of #30DaysOfSpacelift content easier...

This video is an excellent overview of Spacelift as an alternative to Terraform Cloud! 🚀 It's impressive to see how Spacelift offers a powerful CI/CD platform for managing Terraform workflows and deployments. Thanks for sharing this valuable resource! 👍

Lovely movies, but you do talk a bit fast! Even for an English near native speaker it is hard to think, remember and listen at you simultaneously for 20 minutes!

Contents: 00:00 Introduction 00:27 Spacelift Migration Tool Overview 01:06 Demo Part 1: Prerequisites (API keys, VCS integration...etc) 03:40 Demo Part 2: Exporting Terraform Cloud workspaces 06:57 Demo Part 3: Generate Terraform code for Spacelift resources 09:04 Demo Part 4: Create Spacelift Manager Stack 13:22 Demo Part 5: Clean up tasks 14:42 Caveats and Limitations 16:01 Conclusions

00:10 Introduction 01:28 Workspaces vs Stacks 03:43 Terraform State Management 04:20 Blueprints 05:02 Runtime Environment 06:11 Cloud Integration 06:55 Key Differences - Summary of Overview 07:24 Compliance (Policy as Code) 10:20 Security (Custom Inputs) 11:42 GitOps & GitHub Integration 13:55 User management & RBAC 16:20 Module Registry 17:55 Pricing

Hope that access key and secret has been removed

Simple straight and perfect demo, This is just a very good way to get up to speed working with spacelift. Thanks a lot

00:11 - Introduction 02:57 - Setting up our first Spacelift Stack 07:42 - Connecting Spacelift to AWS 11:12 - Triggering our first Terraform run in Spacelift 15:24 - Introducing Spacelift Policies 21:45 - Conclusions and overview of Spacelift pricing and comparison to Terraform Cloud

Hey Team, liking the look of the product and im seeing it quite often. However, what's the sell? It looks like a standard release pipeline and I can have policies configured in my tenant. What it the USP for this product?

Hello! Great video! In 2:26 when you open a pull request I think you meant "updated instance to t2.large".

Great demo.

Have a good day 🐻🐻🐻🦄🦄🦄🐶🐶🐶🦋🦋🦋🦕🦕🦕

first

Policies everywhere!

Passwords never belong in repositories. I strongly advise you to change this example. This is incredibly bad security hygiene and developers should never store passwords in a distributed version control system.