Skip to content
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

Space application supporter deployments wip #1

Conversation

will-gant
Copy link

@will-gant will-gant commented Jul 1, 2021

.

dependabot bot and others added 30 commits June 2, 2021 11:17
Bumps [sequel](https://github.com/jeremyevans/sequel) from 5.44.0 to 5.45.0.
- [Release notes](https://github.com/jeremyevans/sequel/releases)
- [Changelog](https://github.com/jeremyevans/sequel/blob/master/CHANGELOG)
- [Commits](jeremyevans/sequel@5.44.0...5.45.0)

---
updated-dependencies:
- dependency-name: sequel
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
- Add tests that check permissions.
- Adjust documentation; "All Roles" are permitted.
- Add 'space_application_supporter' to permission tests.
- Remove 'set_current_user_as_role' from "when the user is logged in"
  context; for this test only the scope (cloud_controller.read) is
  important.
- Add tests that check permissions.

Co-authored-by: Will Gant <[email protected]>
* Refactored v3 Events permissions checks to be in the permissions
queryer because we believe that to be the desired pattern + easier to
follow.
* Updated documentation.

[cloudfoundry#2216]

Co-authored-by: Carson Long <[email protected]>
Co-authored-by: Mona Mohebbi <[email protected]>
Also adds missing table headers for roles tables that have notes, as the absence of these prevents the second column from rendering.
Manifest diff changes at the application are now ignored if there isn't
a sub attribute.
…e-columns

Use a consistent format for roles table notes in API docs
…ion-supporter-events

Allow Space Application Supporter access to specific Audit Events endpoints
…lication-supporter-jobs

Ensure that space application supporter can access GET /v3/jobs/:guid
…lication-supporter-users

Ensure that space application supporter can access user GET endpoints
* Decided to have some fields in v3/droplets/:guid be redacted (in a
similar fashion to every role except admin roles and space developers)
* Updated documentation
* Refactored some of the droplets request specs to use it_behaves_like

[cloudfoundry#2220]

Co-authored-by: Weyman Fung <[email protected]>
Co-authored-by: Carson Long <[email protected]>
…lication-supporter-buildpacks

Ensure that space application supporter can get/list buildpacks
…lication-supporter-environment-variable-groups

Space application supporter can access environment variable groups
…dler/sequel-5.45.0

build(deps): bump sequel from 5.44.0 to 5.45.0
)

Test list, get package endpoints for all roles
…ion-supporter-droplets

Allow space application supporter to access specific droplet endpoints
Bundler prefers "with_unbundled_env" over the old "with_clean_env"

Co-authored-by: Matthew Kocher <[email protected]>
Co-authored-by: Mona Mohebbi <[email protected]>
will-gant and others added 12 commits June 23, 2021 11:01
This reverts commit a50aef2. See pull request cloudfoundry#2323 for discussion on the decision not to grant the space application supporter access to PATCH endpoints that only allow users to update metadata/labels: cloudfoundry#2323 (comment)
See pull request cloudfoundry#2323 for discussion on the decision not to grant the space application supporter access to PATCH endpoints that only allow users to update metadata/labels: cloudfoundry#2323 (comment)
Signed-off-by: Aftab Alam <[email protected]>
Signed-off-by: Aftab Alam <[email protected]>
@will-gant will-gant closed this Jul 1, 2021
@will-gant
Copy link
Author

Created by mistake - please ignore.

philippthun pushed a commit that referenced this pull request Jun 15, 2022
Notable changes in this commit:
* Adds an `/internal/v4/metrics` endpoint which serves Prometheus-style
metrics.
* Adds function to Prometheus::Client::Registry to re-create the
library's metrics registry. This is used by the PrometheusClient class's
tests to wipe out the metrics registry, which is global state. Global
state is the #1 cause of test pollution and this change seemed to be the
most straightforward way to eliminate some order-dependent test failures.
NOTE: This function definition is only in the
`prometheus_updater_spec.rb` file, which we believe is not shipped in
capi-release, so the odds of actually writing production code that
depends on this test-only functionality are pretty slim.

Co-authored-by: David Alvarado <[email protected]>
Co-authored-by: Kenneth Lakin <[email protected]>
Co-authored-by: Merric de Launey <[email protected]>
Co-authored-by: Michael Oleske <[email protected]>
will-gant pushed a commit that referenced this pull request Dec 16, 2022
Notable changes in this commit:
* Adds an `/internal/v4/metrics` endpoint which serves Prometheus-style
metrics.
* Adds function to Prometheus::Client::Registry to re-create the
library's metrics registry. This is used by the PrometheusClient class's
tests to wipe out the metrics registry, which is global state. Global
state is the #1 cause of test pollution and this change seemed to be the
most straightforward way to eliminate some order-dependent test failures.
NOTE: This function definition is only in the
`prometheus_updater_spec.rb` file, which we believe is not shipped in
capi-release, so the odds of actually writing production code that
depends on this test-only functionality are pretty slim.

Co-authored-by: David Alvarado <[email protected]>
Co-authored-by: Kenneth Lakin <[email protected]>
Co-authored-by: Merric de Launey <[email protected]>
Co-authored-by: Michael Oleske <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants