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

Return correct response for creating instances and bindings that alre… #240

Merged
merged 1 commit into from
Oct 6, 2021

Conversation

shiresky
Copy link
Contributor

@shiresky shiresky commented May 7, 2021

Overview

aws-servicebroker does not implement OSB specification correctly. It causes issues with creating K8s service catalog ServiceInstances and ServiceBindings representations for instances and bindings that already exists in broker's database (were created previously with use of plain OSB API).

Testing

Changes were tested by:

  • creating RDS MariaDB and its binding with use of OSB API
  • creating RDS MariaDB and its binding with use of OSB API and after that recreating them with use of OSB API
  • creating RDS MariaDB and its binding with use of OSB API and after that recreating them with use of K8s service catalog

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@shiresky shiresky requested a review from jaymccon as a code owner May 7, 2021 08:02
@shiresky shiresky changed the title [WIP] Return correct response for creating instances and bindings that alre… Return correct response for creating instances and bindings that alre… May 7, 2021
@CsatariGergely
Copy link

@vsomayaji can you please review?

@jaymccon
Copy link
Contributor

jaymccon commented Oct 6, 2021

Apologies for the delay @shiresky and thank you for the contribution. Merging now and will hopefully have a new release cut shortly.

@jaymccon jaymccon merged commit 2386855 into awslabs:main Oct 6, 2021
@jaymccon
Copy link
Contributor

jaymccon commented Oct 6, 2021

after doing some testing for release it seems this pr is causing a few tests to fail, I'm going to revert this merge to unblock release for the time being.

@shiresky if you would still like this merged can you please have a look at the failing tests, resolve and open a new pr.

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.

None yet

3 participants