cloudfoundry / cloudfoundry/cloud_controller_ng

Binding Application Security Groups by organization admin

Open
#1,441 3 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature-request networking unscheduled
Dominant language
Ruby
Stars
207
Forks
373
Avg merge
2d 12h
Merged PRs (30d)
56

Description

Issue

My goal is to create definition of a security group as a CF admin and let an organization admin bind them to his spaces. For example, there are 2 orgs: orgA and orgB and 4 user-provided-services:

  • orgA-dbProd
  • orgA-dbDev
  • orgB-dbProd
  • orgB-dbDev

I want to create them as the CF admin :

# orgA
cf create-security-group orgA-dbProd ./orgA-dbProd.json
cf create-security-group orgA-dbDev ./orgA-dbDev.json
# orgB
cf create-security-group orgB-dbProd ./orgB-dbProd.json
cf create-security-group orgB-dbDev ./orgB-dbDev.json

and give the org admins rights to bind them to the org spaces:

# orgA
cf allow-bind-security-group orgA-dbProd orgA
cf allow-bind-security-group orgA-dbDev orgA
# orgB
cf allow-bind-security-group orgB-dbProd orgB
cf allow-bind-security-group orgB-dbDev orgB

and now the CF admin should be able to bind them to the selected spaces.

Context

As the CF admin I don't want to have knowledge about org spaces configuration.
My responsibility is to configure org-level and let org-admin do his config.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No implementation files or tests are named. Start by tracing the Cloud Controller entry points for create-security-group and allow-bind-security-group, then examine how organization-admin permissions relate to space binding. Done means an organization admin can bind CF-admin-created security groups to spaces in that organization, with coverage for the orgA/orgB scenarios described.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
api, backend, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.