worried-xylophone-86184
09/01/2022, 6:19 PMbillowy-army-68599
09/01/2022, 6:20 PMPulumi.<stack>.yaml
>worried-xylophone-86184
09/02/2022, 3:47 AMPulumi.<stack>.yaml
One section of the stack file is something like this
vpc:
create: false
existing_vpc_details:
id: XYZ
cidr-range: 10.0.0.0/16
public_subnets:
zone-a: "XYZ"
zone-b: "XYZ"
private_subnets:
zone-a: "XYZ"
zone-b: "XYZ"
s3_ingest_config:
zones:
- zone-a
- zone-b
db_cluster:
instance_type: db.t3.small
root_password: XYZ
launch_reader_writer: false # Set to false for dev/QA setups
# Minimum 2 zones required: <https://tinyurl.com/3zs4ujvm>
zones:
- zone-a
- zone-b
cp_live:
bucket_lifecycle: 30 # in days
redis:
instance_type: cache.t3.micro
password: XYZ
zones:
- zone-a
- zone-b
where in users are allowed to configure the instance type etc.
We have validations in place which check if these configurations have been done correctly.
In a scenario where the STACK has already been brought up and some one wants to modify something say the RDS Instance type and there is a mistake in the STACK configuration file, our code has been designed in a such a way that the deployment of resources does not proceed but Pulumi treats that as a destroy operation.billowy-army-68599
09/02/2022, 3:53 AMpulumi.log.error("misconfiguration detected!")
which will stop the program from executingworried-xylophone-86184
09/02/2022, 4:11 AMsys.exit()
in pulumi?billowy-army-68599
09/02/2022, 4:11 AMworried-xylophone-86184
09/02/2022, 4:12 AMbillowy-army-68599
09/02/2022, 4:13 AMworried-xylophone-86184
09/02/2022, 4:14 AM