New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import notify-management space #931
base: main
Are you sure you want to change the base?
Conversation
Terraform Format and Style: success Show Plan
Pusher: @jskinne3, Action: |
Terraform Format and Style: success Show Plan
Pusher: @jskinne3, Action: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @jskinne3!
Noting here that this'll require a rebase with main
once the first batch of PRs are merged when we're ready.
import { | ||
to = cloudfoundry_space.notify-management | ||
id = "a022fabe-056c-4329-9d4f-3f7a67442d36" | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Calling out the fact that with the way this is done, which is very straightforward and makes sense, I'm assuming this'll be the approach for the other spaces that aren't currently under Terraform management (e.g., notify-staging
)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup! This is the technique I think we should use to bring other spaces into Terraform
Description
Importing the
notify-management
space under Terraform management, with aprevent_destroy
on itDeployment