mirror of
https://github.com/GSA/notifications-api.git
synced 2025-12-24 01:11:38 -05:00
1484c2ffa0
The SES and SNS modules are strictly for services that are instantiated within a space, while the egress_space is creating a separate space. The shift of the recursive delete from being on a service to being at the space level means that the SES and SNS modules do not have to track it at all, it should only be handled at the space level. The same goes for the allow_ssh flag. Signed-off-by: Carlo Costino <carlo.costino@gsa.gov>
25 lines
558 B
HCL
25 lines
558 B
HCL
variable "cf_org_name" {
|
|
type = string
|
|
description = "cloud.gov organization name"
|
|
}
|
|
|
|
variable "cf_space_name" {
|
|
type = string
|
|
description = "cloud.gov space name (staging or prod)"
|
|
}
|
|
|
|
variable "name" {
|
|
type = string
|
|
description = "name of the service instance"
|
|
}
|
|
|
|
variable "aws_region" {
|
|
type = string
|
|
description = "AWS region the SNS settings are set in"
|
|
}
|
|
|
|
variable "monthly_spend_limit" {
|
|
type = number
|
|
description = "SMS budget limit in USD. Support request must be made before raising above 1"
|
|
}
|