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

As a Korifi API user I want to be able to create service brokers #3263

Closed
danail-branekov opened this issue May 22, 2024 · 0 comments
Closed

Comments

@danail-branekov
Copy link
Member

As a Korifi API user I want to be able to create service brokers

GIVEN I have not enabled the experimental managed services flag in the helm values
WHEN I POST /v3/service_brokers
THEN I get a 422 Unprocessable Entity Error explaining that managed services support is not enabled

GIVEN I have enabled the experimental managed services flag in the helm values
WHEN I POST /v3/service_brokers
THEN I get a 202 Accepted response with a Location header pointing me to the broker creation job
WHEN I curl the broker creation job
THEN I get proper job response
THEN I eventually see the creation job succeeding

Dev notes:

@github-project-automation github-project-automation bot moved this to 🧊 Icebox in Korifi - Backlog May 22, 2024
@danail-branekov danail-branekov moved this from 🧊 Icebox to 🇪🇺 To do in Korifi - Backlog May 31, 2024
@danail-branekov danail-branekov moved this from 🇪🇺 To do to 🔄 In progress in Korifi - Backlog May 31, 2024
@danail-branekov danail-branekov self-assigned this May 31, 2024
danail-branekov added a commit that referenced this issue Jun 10, 2024
* Globally available brokers are only supported (space-restricted
  brokers are currently out of scope)
* Introduce the `CFServiceBroker` custom resource
* The `CFServiceBroker` controller sets its `Ready` state
* Implement `POST /v3/service_brokers`
* Only allow admin users to create brokers
* The `CFServiceBroker` object is created in the root namespace (as it
  is globally available)
* Implement `GET /v3/jobs/service_broker.create~<broker-guid>` to return
  `COMPLETE` job state once the broker is ready
* Validate broker name uniqueness via a validating webhook

fixes #3263
danail-branekov added a commit that referenced this issue Jun 10, 2024
* Globally available brokers are only supported (space-restricted
  brokers are currently out of scope)
* Introduce the `CFServiceBroker` custom resource
* The `CFServiceBroker` controller sets its `Ready` state
* Implement `POST /v3/service_brokers`
* Only allow admin users to create brokers
* The `CFServiceBroker` object is created in the root namespace (as it
  is globally available)
* Implement `GET /v3/jobs/service_broker.create~<broker-guid>` to return
  `COMPLETE` job state once the broker is ready
* Validate broker name uniqueness via a validating webhook

fixes #3263
danail-branekov added a commit that referenced this issue Jun 10, 2024
* Globally available brokers are only supported (space-restricted
  brokers are currently out of scope)
* Introduce the `CFServiceBroker` custom resource
* The `CFServiceBroker` controller sets its `Ready` state
* Implement `POST /v3/service_brokers`
* Only allow admin users to create brokers
* The `CFServiceBroker` object is created in the root namespace (as it
  is globally available)
* Implement `GET /v3/jobs/service_broker.create~<broker-guid>` to return
  `COMPLETE` job state once the broker is ready
* Validate broker name uniqueness via a validating webhook

fixes #3263
danail-branekov added a commit that referenced this issue Jun 11, 2024
* Globally available brokers are only supported (space-restricted
  brokers are currently out of scope)
* Introduce the `CFServiceBroker` custom resource
* The `CFServiceBroker` controller sets its `Ready` state
* Implement `POST /v3/service_brokers`
* Only allow admin users to create brokers
* The `CFServiceBroker` object is created in the root namespace (as it
  is globally available)
* Implement `GET /v3/jobs/service_broker.create~<broker-guid>` to return
  `COMPLETE` job state once the broker is ready
* Validate broker name uniqueness via a validating webhook

fixes #3263
georgethebeatle added a commit that referenced this issue Jul 2, 2024
* Globally available brokers are only supported (space-restricted
  brokers are currently out of scope)
* Introduce the `CFServiceBroker` custom resource
* The `CFServiceBroker` controller sets its `Ready` state
* Implement `POST /v3/service_brokers`
* Only allow admin users to create brokers
* The `CFServiceBroker` object is created in the root namespace (as it
  is globally available)
* Implement `GET /v3/jobs/service_broker.create~<broker-guid>` to return
  `COMPLETE` job state once the broker is ready
* Validate broker name uniqueness via a validating webhook

fixes #3263

Co-authored-by: Danail Branekov <[email protected]>
@github-project-automation github-project-automation bot moved this from 🔄 In progress to ✅ Done in Korifi - Backlog Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

1 participant