-
Notifications
You must be signed in to change notification settings - Fork 204
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
Azure API management service #20
Comments
jananivMS
changed the title
API Management Operator
As a user, I can configure and deploy Azure API management service by specifying a CRD in the Kubernetes YAML file
Aug 1, 2019
frodopwns
changed the title
As a user, I can configure and deploy Azure API management service by specifying a CRD in the Kubernetes YAML file
Azure API management service
Aug 5, 2019
This was referenced Aug 5, 2019
Closed
1 task
This was referenced Aug 7, 2019
Closed
Closed
4 tasks
This is complete now |
jananivMS
pushed a commit
that referenced
this issue
May 15, 2020
CosmosDB test region workaround (#896)
Porges
pushed a commit
that referenced
this issue
May 11, 2021
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This epic covers
Development of an Azure Service operator using Kubebuilder which creates a CRD for Azure API management
An user should be able to deploy/delete/update the resource
We'll use Azure Go SDK for the resource management/creation
There will need to be tests and logging added
Acceptance criteria
Reference: [Done-Done checklist] Link
Can you create, delete and update settings for the Azure API Management service?
Are there unit tests for the resource helper functions?
Are there integration tests that run as part of the release pipeline?
Is there logging and telemetry added for diagnosability?
Is there documentation added for how to deploy and use the operator?
Code reviewed by product group?
Code reviewed by customer?
User Stories
Add links to User Stories for this epic. User stories are intended to be completed in one sprint.
The text was updated successfully, but these errors were encountered: