enterprise-setup
enterprise-setup copied to clipboard
Installation resources for CircleCI Enterprise
Throws warning, that will soon become errors if not addressed. ``` Warning: Interpolation-only expressions are deprecated on modules/aws_sqs/main.tf line 27, in resource "aws_iam_role_policy" "mod_role_policy": 27: role = "${aws_iam_role.mod_role.id}" ``` Terraform...
https://groups.google.com/forum/#!topic/terraform-tool/hEESOVOgL_Q Not with Terraform, but it's pretty easy to stop and start an instance with the CLI tools if you have them installed: $ aws ec2 stop-instances --region us-east-2 --instance-ids...
see https://github.com/circleci/enterprise-setup/blob/master/templates/services_user_data.tpl#L20 ens3 is not always a valid device name. Without this env var set the install fails. Since this is aws specific you can use the metadata url to...
I began creating some Alarms, scaling policies, and what have you to ensure CircleCI workers scaled based on the threshold end users provided, but later stumbled across: https://circleci.com/docs/enterprise/cloudwatch/ It wasn't...
Currently, due to other services not being in AWS, our team uses `dnsmasq` to route traffic to specific domains. `dnsmasq` is installed on the service box, but the service box...
Currently, the only way to run this script is with secrets. Secrets are not very useful when your company authenticates your AWS accounts via CLI and stores the AWS temp...
Currently, the enterprise setup script always generates an elastic ip for the service box. This is not something we are comfortable with since that exposes it to the entire web...
I've been trying to set this up for the last few days at our company, and I've found that this repo may need a major overhaul to accomplish this. We...
Since this is being deployed to enterprise customers, the quad zero domain is usually frowned upon as it is not very secure. Most of the traffic that needs to occur...