cloudfoundry / cloudfoundry/cloud_controller_ng
Bosh-DNS names as destination Application Security Group
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 207
- Forks
- 373
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 56
Description
Issue
I want to use Bosh-DNS names as a destination in an Application Security Group definition.
Example:
[
{
"destination": "q-s0.postgres-instance.default.postgres-deployment.bosh",
"ports": "5432",
"protocol": "tcp"
}
]
Now I can use it in user-provided-services definition, but ASG destination doesn't support host names.
Context
One source of truth is usually a good idea.
I think BOSH-DNS is source of truth about IP addresses, so why don't use it in an Application Security Group definition.
BTW, until openstack will not support local static IP (https://github.com/cloudfoundry/bosh-openstack-cpi-release/issues/14), using BOSH-DNS names can be walkaround. Local IP addresses can be changed automatically by bosh-director... then ASG definitions have outdated information.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Start with Application Security Group destination handling and compare it with user-provided-services definitions, using the BOSH-DNS destination example as the expected case. Done means ASG definitions can use BOSH-DNS names as destinations without requiring manually maintained IP addresses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100