cloudfoundry / cloudfoundry/cloud_controller_ng
Buildpack Visibility
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 207
- Forks
- 373
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 56
Description
Thanks for submitting an issue to cloud_controller_ng. We are always trying to improve! To help us, please fill out the following template.
Issue
I have a basic question with respect to the Build-pack Visibility across our Environments
We would like to understand if there is an option to hide / unhide build-packs in specific environments for any obvious purposes
What I am trying to say is,
When i create a buildpack using the cf create-buildpack , i want to hide this buildpack with respect to specific Org and Space.
So when a specific user logs into CF with his account , he should not be able to see the buildpacks that we wish to hide
Context
I should be able to hide / unhide buildpacks according to the users at Org level or space level
Steps to Reproduce
cf api
cf login
cf buildpacks
Expected result
We as a CF admin should be able to hide / unhide buildpacks at Org or Space levels depending on the users
Current result
Unable to hide / unhide buildpacks that are shown from the cf buildpacks command
All Orgs and Spaces display the same result as that of the cf buildpacks command
Possible Fix
Can enable the CC-DB show up the created build pack to display results like the cf service-access. BPs should be able to be hid / unhid
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
Start with the cf create-buildpack and cf buildpacks entry points, then review the Cloud Controller database and cf service-access behavior mentioned in the possible fix. Clarify the intended Org- and Space-level visibility rules; done means an admin can hide or unhide buildpacks so users in the selected scopes see the expected buildpack list.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- authorization, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100