-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add SMTP brokerpak and supporting #5
Conversation
Also update the Dockerfile to build it. Source: https://github.com/GSA-TTS/datagov-brokerpak-smtp
They're the same underlying value, but looking at the outputs alone, you wouldn't know that.
Download the Terraform provider from GitHub to follow Hashi registry ToS
And Dockerfiles are unused
<oh my god>
- Remove txt_verification_record which is redundant with DKIM records - Mirror tags from https://github.com/cloud-gov/go-broker-tags/blob/main/tags.go#L10
This reverts commit c2954f2.
Goal is to minimize disruption of updates. Resolves: cloud-gov/product#3123
Uses workaround to HIL parser limitation here: cloudfoundry/cloud-service-broker#1086 (comment)
value = aws_iam_access_key.access_key.id | ||
} | ||
|
||
# TODO should we only expose the SMTP interface? |
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.
What would this mean?
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.
The binding provides a set of SMTP credentials and an AWS access key to the IAM user, which allows customers to use the AWS SES APIs instead of the SMTP interface. I'll take this TODO out, though; it's a desirable behavior so they can use the AWS SDK if they want, and the security impact is the same since the user has privileges limited to their identity only.
tags = { | ||
"broker" = "Cloud Service Broker" | ||
"client" = "Cloud Foundry" | ||
"environment" = "local" # todo, parameterize at CSB level |
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.
I assume we'll follow up on this later
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.
Yep, that's probably in my next issue, which is tackling Terraform for deploying the broker itself.
Changes proposed in this pull request:
Things to check
INFO
and debugging statements are written withlog.debug
or similar, then they won't be written to the otput, which can prevent unintentional leaks of sensitive data.Security considerations
Follows standard practices to avoid credential disclosure.