From dymurray at redhat.com Fri Sep 1 14:09:52 2017 From: dymurray at redhat.com (Dylan Murray) Date: Fri, 1 Sep 2017 10:09:52 -0400 Subject: [Ansible-service-broker] Reconfiguring automated build process Message-ID: All, Since we have split out the apb-examples repo it broke some of the automated build process. With some great help by Jason the Jenkins system is just about complete and what's left is recreating the Dockerhub images to point to the new source repositories. Unfortunately the only way to do this is to delete and recreate the repos. I don't expect this to impact anyone for more than 30 minutes as I will push the latest images back up and trigger the canary builds immediately. Please bear with me if you experience some downtime. Thanks, Dylan -------------- next part -------------- An HTML attachment was scrubbed... URL: From dymurray at redhat.com Fri Sep 1 14:55:56 2017 From: dymurray at redhat.com (Dylan Murray) Date: Fri, 1 Sep 2017 10:55:56 -0400 Subject: [Ansible-service-broker] Reconfiguring automated build process In-Reply-To: References: Message-ID: All, The builds have been successfully switched over to the new repos. Some are still building the canary tag but they all have 'latest' and 'sprint136'. Please let me know if you are still seeing problems. Huge thanks to Jason for the help. Dylan On Fri, Sep 1, 2017 at 10:09 AM, Dylan Murray wrote: > All, > > Since we have split out the apb-examples repo it broke some of the > automated build process. With some great help by Jason the Jenkins system > is just about complete and what's left is recreating the Dockerhub images > to point to the new source repositories. Unfortunately the only way to do > this is to delete and recreate the repos. > > I don't expect this to impact anyone for more than 30 minutes as I will > push the latest images back up and trigger the canary builds immediately. > Please bear with me if you experience some downtime. > > Thanks, > Dylan > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shurley at redhat.com Sat Sep 2 02:16:48 2017 From: shurley at redhat.com (Shawn Hurley) Date: Fri, 1 Sep 2017 22:16:48 -0400 Subject: [Ansible-service-broker] Ansible Service Broker builds failure Message-ID: Hello All, I am noticing that the broker builds seem to be failing, it appears that the broker itself is working, but that the CI part of the job is failing. 1. I am wondering if anyone thinks it could be related to moving repos/rebuilds? 2. It also could be a bug in the secrets PR that was merged in? I will be looking into the second one if someone with a little more understanding of the CI process could take a look at 1? Thanks, Shawn From fabian at redhat.com Tue Sep 5 15:41:18 2017 From: fabian at redhat.com (Fabian von Feilitzsch) Date: Tue, 5 Sep 2017 11:41:18 -0400 Subject: [Ansible-service-broker] Broker secrets In-Reply-To: References: Message-ID: My PR allowing you to use secrets to pass sensitive parameters into APBs was just merged. The PR was motivated by our work on Amazon APBs, where we have highly sensitive credentials, as well as cluster-specific configuration that the user shouldn't have to deal with. Our solution, at least until the OpenServiceBroker API supports secret passing between the catalog and broker, is to have a project administrator create a secret in the namespace of the broker, and update the broker configuration to associate that secret with a specific APB. On the next catalog request to the broker, any parameters provided by that secret should be filtered from the spec, so the user will not be prompted for them. Any APB that has associated secrets will run in the namespace of the broker and with the secrets mounted. The APB base image has been updated to handle parsing those mounted secrets into a format consumable by ansible, as well as to disable ansible logging to prevent the credentials from showing up in plain text. I also included a python script (scripts/create_broker_secret.py in the ansible-service-broker project) that should make interacting with the secret changes pretty simple. It will allow you to specify a secret name, namespace of the broker, and image you'd like to associate, as well as a series of key=value pairs or yaml formatted files, and it will create the corresponding secret, update the broker configuration, and rollout a new broker if necessary. As an unexpected side-benefit, I've actually found this change very useful for testing, because I was able to specify parameters in the secret and never had to enter them again. I mostly tested with the rhscl-postgresql-apb, using the following secret: ./scripts/create_broker_secret.py test ansible-service-broker docker.io/fabianvf/rhscl-postgresql-apb postgresql_user=admin postgresql_password=changeme postgresql_version="9.5" It really did speed up my testing cycles a lot. Full usage output for the script: ??? ./scripts/create_broker_secret.py --help USAGE: ./scripts/create_broker_secret.py NAME NAMESPACE IMAGE [KEY=VALUE]* [@FILE]* NAME: the name of the secret to create/replace NAMESPACE: the target namespace of the secret. It should be the namespace of the broker for most usecases IMAGE: the docker image you would like to associate with the secret KEY: a key to create inside the secret. This cannot contain an "=" sign VALUE: the value for the KEY in the secret FILE: a yaml loadable file containing key: value pairs. A file must begin with an "@" symbol to be loaded EXAMPLE: ./scripts/create_broker_secret.py mysecret ansible-service-broker docker.io/ansibleplaybookbundle/hello-world-apb key1=hello key2=world @additional_parameters.yml -------------- next part -------------- An HTML attachment was scrubbed... URL: From shurley at redhat.com Tue Sep 5 19:58:32 2017 From: shurley at redhat.com (Shawn Hurley) Date: Tue, 5 Sep 2017 15:58:32 -0400 Subject: [Ansible-service-broker] User Impersonation Proposal Message-ID: <3b3a70f8-af0a-aa9a-77d9-f35f853d7711@redhat.com> Hello all, I have a proposal out for impersonating a user. This proposal is something that I would like to discuss at stand up on Thursday. The condensed proposal is here: https://github.com/openshift/ansible-service-broker/pull/418 A longer more detailed write up by John Matthews is here: https://docs.google.com/a/redhat.com/document/d/1VqFhtt7viZg8G4Dl1Kh_ayLLAoVWDahBP8rcokcYRsY/edit?usp=sharing Thanks, Shawn Hurley From rhallise at redhat.com Fri Sep 8 16:55:31 2017 From: rhallise at redhat.com (Ryan Hallisey) Date: Fri, 8 Sep 2017 12:55:31 -0400 Subject: [Ansible-service-broker] service-catalog resource name changes Message-ID: Hey Folks, A bunch of the service-catalog resources changed names for 1.7. Here are the name changes from patch [#1](https://github.com/kubernetes-incubator/service-catalog/commit/33cb34575a461887ad270a13a08ed712d3023949). Brokers() -> ServiceBrokers(), Instances() -> ServiceInstances(), Bindings() -> ServiceInstanceCredentials(), BrokerRelistInterval -> s.ServiceBrokerRelistInterval, -Ryan From rhallise at redhat.com Tue Sep 12 13:36:54 2017 From: rhallise at redhat.com (Ryan Hallisey) Date: Tue, 12 Sep 2017 09:36:54 -0400 Subject: [Ansible-service-broker] Tagging before 3.7 Message-ID: Hey Team, There are some PRs up that allow the broker to work with OpenShift 3.7. I want to make sure that before we merge anything that is 3.7 specific, we talk about tagging the broker that works with 3.6. This will make sure that anyone consuming the broker downstream on 3.6 doesn't break. Let me know your thoughts. We can discuss more at today's meeting. -Ryan From shurley at redhat.com Tue Sep 12 13:40:02 2017 From: shurley at redhat.com (Shawn Hurley) Date: Tue, 12 Sep 2017 09:40:02 -0400 Subject: [Ansible-service-broker] Tagging before 3.7 In-Reply-To: References: Message-ID: On 09/12/2017 09:36 AM, Ryan Hallisey wrote:> Let me know your thoughts. We can discuss more at today's meeting. +1 I would think that we should discuss at either stand up or team meeting tomorrow. From jmatthew at redhat.com Tue Sep 12 14:01:44 2017 From: jmatthew at redhat.com (John Matthews) Date: Tue, 12 Sep 2017 10:01:44 -0400 Subject: [Ansible-service-broker] Tagging before 3.7 In-Reply-To: References: Message-ID: I'd like to see if we can maintain a single binary that works on 3.6 and 3.7 for ~next month opposed to branching/forking code now. Thought is, check for capability, if it exists use it, if it doesn't error out. For something like the User Impersonation feature of "auto_escalate: False" we require newer APIs in 3.7, but we can error out if running on 3.6. This allows the same broker binary to continue to work on 3.6 for next month while 3.7 issues are being flushed out. On Tue, Sep 12, 2017 at 9:40 AM, Shawn Hurley wrote: > On 09/12/2017 09:36 AM, Ryan Hallisey wrote:> Let me know your thoughts. > We can discuss more at today's meeting. > +1 > > I would think that we should discuss at either stand up or team meeting > tomorrow. > > > _______________________________________________ > Ansible-service-broker mailing list > Ansible-service-broker at redhat.com > https://www.redhat.com/mailman/listinfo/ansible-service-broker > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cchase at redhat.com Wed Sep 13 15:33:23 2017 From: cchase at redhat.com (Christopher Chase) Date: Wed, 13 Sep 2017 11:33:23 -0400 Subject: [Ansible-service-broker] Video - APB Field Entry UX Improvements Message-ID: I published the demo detailing the enhancements to the user experience when entering APB parameters. Hopefully this will allow APB authors to craft a better experience for their users. https://www.youtube.com/watch?v=6evF2r9FJmI Thanks, Chris Chase -------------- next part -------------- An HTML attachment was scrubbed... URL: From shurley at redhat.com Thu Sep 14 20:14:27 2017 From: shurley at redhat.com (Shawn Hurley) Date: Thu, 14 Sep 2017 16:14:27 -0400 Subject: [Ansible-service-broker] APB Test Video Message-ID: <0e850d9c-674b-27fc-0847-ef88afbb45fe@redhat.com> Hello All, I have published a video demo of the APB test playbook that we added last iteration. If you want to watch the video the link is: https://youtu.be/jTBQ3-YYzzo Thanks, Shawn Hurley From dymurray at redhat.com Fri Sep 15 13:37:26 2017 From: dymurray at redhat.com (Dylan Murray) Date: Fri, 15 Sep 2017 09:37:26 -0400 Subject: [Ansible-service-broker] Keycloak APB Binding Demos Message-ID: All, I have published two videos demonstrating different binding workflows with Keycloak APB. The first is an example of binding to a nodejs+express app. This APB (Keypress) creates a realm and a list of users during bind and then displays some information around Keycloak in a UI. The second is an example of binding to a python/flask app. This application takes a user/pass combo as input and creates a user in the already created realm using Keycloaks binding secret. It then updates the client to point to the python app's URL. https://www.youtube.com/watch?v=6kk-MaXTXOo https://www.youtube.com/watch?v=O8W_DWPwYCY Enjoy, Dylan -------------- next part -------------- An HTML attachment was scrubbed... URL: From dymurray at redhat.com Wed Sep 20 12:56:16 2017 From: dymurray at redhat.com (Dylan Murray) Date: Wed, 20 Sep 2017 08:56:16 -0400 Subject: [Ansible-service-broker] Fwd: JDG Online Service and Ansible Service Broker In-Reply-To: References: Message-ID: Forwarding Sebastian's message to our new listserv. ---------- Forwarded message ---------- From: Sebastian Laskawiec Date: Wed, Sep 20, 2017 at 8:50 AM Subject: JDG Online Service and Ansible Service Broker To: ansibleapps-internal Cc: Gustavo Fernandes , Pedro Zapata Fernandez < pzapataf at redhat.com>, "Tarrant, Tristan" Hey, My name is Sebastian and I'm one of the devs working on Infinispan/JBoss Data Grid projects. A while ago we came up with an idea about new type of services we could introduce to the OpenShift users. We plan to bootstrap those services using Ansible Service Broker. Having this in mind, I'd like to ask a couple of questions: - The Ansible Service Broker uses built APBs (Docker images). Is there any support for building APBs for Brew [1] (just in case - Brew is a productization tool that is used to build all Red Hat products). - Do you plan to integrate with OpenShift Online? If so, how can we plug our APBs there? - Do you plan to integration with Open PaaS [2]? If so - the same question as the above... Thanks, Sebastian [1] https://brewweb.devel.redhat.com [2] https://open.paas.redhat.com/console/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmatthew at redhat.com Wed Sep 20 13:25:20 2017 From: jmatthew at redhat.com (John Matthews) Date: Wed, 20 Sep 2017 09:25:20 -0400 Subject: [Ansible-service-broker] Fwd: JDG Online Service and Ansible Service Broker In-Reply-To: References: Message-ID: On Wed, Sep 20, 2017 at 8:56 AM, Dylan Murray wrote: > Forwarding Sebastian's message to our new listserv. > > > ---------- Forwarded message ---------- > From: Sebastian Laskawiec > Date: Wed, Sep 20, 2017 at 8:50 AM > Subject: JDG Online Service and Ansible Service Broker > To: ansibleapps-internal > Cc: Gustavo Fernandes , Pedro Zapata Fernandez < > pzapataf at redhat.com>, "Tarrant, Tristan" > > > Hey, > > My name is Sebastian and I'm one of the devs working on Infinispan/JBoss > Data Grid projects. A while ago we came up with an idea about new type of > services we could introduce to the OpenShift users. We plan to bootstrap > those services using Ansible Service Broker. > > Having this in mind, I'd like to ask a couple of questions: > > - The Ansible Service Broker uses built APBs (Docker images). Is there > any support for building APBs for Brew [1] (just in case - Brew is a > productization tool that is used to build all Red Hat products). > > Yes, we currently have 2 APB examples built in brew: rhscl-postgresql and mediawiki > > - Do you plan to integrate with OpenShift Online? If so, how can we > plug our APBs there? > > Yes, OCP 3.7 is first release we plan to integrate with OpenShift Online. Initial plans are we will offer a limited set of APBs available online. > > - Do you plan to integration with Open PaaS [2]? If so - the same > question as the above... > > No specific plans I'm aware of, but don't see any major blockers preventing a similar approach to the Online case if Administrators wanted to enable/configure the ASB. > Thanks, > Sebastian > > [1] https://brewweb.devel.redhat.com > [2] https://open.paas.redhat.com/console/ > > > _______________________________________________ > Ansible-service-broker mailing list > Ansible-service-broker at redhat.com > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmatthew at redhat.com Wed Sep 20 13:47:38 2017 From: jmatthew at redhat.com (John Matthews) Date: Wed, 20 Sep 2017 09:47:38 -0400 Subject: [Ansible-service-broker] Fwd: JDG Online Service and Ansible Service Broker In-Reply-To: References: Message-ID: On Wed, Sep 20, 2017 at 9:25 AM, John Matthews wrote: > > > On Wed, Sep 20, 2017 at 8:56 AM, Dylan Murray wrote: > >> Forwarding Sebastian's message to our new listserv. >> >> >> ---------- Forwarded message ---------- >> From: Sebastian Laskawiec >> Date: Wed, Sep 20, 2017 at 8:50 AM >> Subject: JDG Online Service and Ansible Service Broker >> To: ansibleapps-internal >> Cc: Gustavo Fernandes , Pedro Zapata Fernandez < >> pzapataf at redhat.com>, "Tarrant, Tristan" >> >> >> Hey, >> >> My name is Sebastian and I'm one of the devs working on Infinispan/JBoss >> Data Grid projects. A while ago we came up with an idea about new type of >> services we could introduce to the OpenShift users. We plan to bootstrap >> those services using Ansible Service Broker. >> >> Having this in mind, I'd like to ask a couple of questions: >> >> - The Ansible Service Broker uses built APBs (Docker images). Is >> there any support for building APBs for Brew [1] (just in case - Brew is a >> productization tool that is used to build all Red Hat products). >> >> > Yes, we currently have 2 APB examples built in brew: rhscl-postgresql and > mediawiki > >> >> - Do you plan to integrate with OpenShift Online? If so, how can we >> plug our APBs there? >> >> > Yes, OCP 3.7 is first release we plan to integrate with OpenShift Online. > Initial plans are we will offer a limited set of APBs available online. > > Clarifying this integration. For 3.7, plan is to support the 'dedicated' scenario for OpenShift Online. Don't believe we have plans for integration with fill multi-tenant OpenShift Online just yet. > >> - Do you plan to integration with Open PaaS [2]? If so - the same >> question as the above... >> >> No specific plans I'm aware of, but don't see any major blockers > preventing a similar approach to the Online case if Administrators wanted > to enable/configure the ASB. > > > >> Thanks, >> Sebastian >> >> [1] https://brewweb.devel.redhat.com >> [2] https://open.paas.redhat.com/console/ >> >> >> _______________________________________________ >> Ansible-service-broker mailing list >> Ansible-service-broker at redhat.com >> https://www.redhat.com/mailman/listinfo/ansible-service-broker >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From slaskawi at redhat.com Wed Sep 20 14:21:27 2017 From: slaskawi at redhat.com (Sebastian Laskawiec) Date: Wed, 20 Sep 2017 14:21:27 +0000 Subject: [Ansible-service-broker] Fwd: JDG Online Service and Ansible Service Broker In-Reply-To: References: Message-ID: On Wed, Sep 20, 2017 at 3:47 PM John Matthews wrote: > On Wed, Sep 20, 2017 at 9:25 AM, John Matthews > wrote: > >> >> >> On Wed, Sep 20, 2017 at 8:56 AM, Dylan Murray >> wrote: >> >>> Forwarding Sebastian's message to our new listserv. >>> >>> >>> ---------- Forwarded message ---------- >>> From: Sebastian Laskawiec >>> Date: Wed, Sep 20, 2017 at 8:50 AM >>> Subject: JDG Online Service and Ansible Service Broker >>> To: ansibleapps-internal >>> Cc: Gustavo Fernandes , Pedro Zapata Fernandez < >>> pzapataf at redhat.com>, "Tarrant, Tristan" >>> >>> >>> Hey, >>> >>> My name is Sebastian and I'm one of the devs working on Infinispan/JBoss >>> Data Grid projects. A while ago we came up with an idea about new type of >>> services we could introduce to the OpenShift users. We plan to bootstrap >>> those services using Ansible Service Broker. >>> >>> Having this in mind, I'd like to ask a couple of questions: >>> >>> - The Ansible Service Broker uses built APBs (Docker images). Is >>> there any support for building APBs for Brew [1] (just in case - Brew is a >>> productization tool that is used to build all Red Hat products). >>> >>> >> Yes, we currently have 2 APB examples built in brew: rhscl-postgresql >> and mediawiki >> >>> >>> - Do you plan to integrate with OpenShift Online? If so, how can we >>> plug our APBs there? >>> >>> >> Yes, OCP 3.7 is first release we plan to integrate with OpenShift >> Online. Initial plans are we will offer a limited set of APBs available >> online. >> >> > > Clarifying this integration. For 3.7, plan is to support the 'dedicated' > scenario for OpenShift Online. > Don't believe we have plans for integration with fill multi-tenant > OpenShift Online just yet. > Ok, I'm glad you clarified this. I actually though about multi-tenant version. Our new services are targeted for OpenShift Online scenarios (both starter and pro tiers) in mind so this might actually be a major issue for us... Could you please let me know once it appears somewhere on the roadmap? > > > >> >>> - Do you plan to integration with Open PaaS [2]? If so - the same >>> question as the above... >>> >>> No specific plans I'm aware of, but don't see any major blockers >> preventing a similar approach to the Online case if Administrators wanted >> to enable/configure the ASB. >> >> >> >>> Thanks, >>> Sebastian >>> >>> [1] https://brewweb.devel.redhat.com >>> [2] https://open.paas.redhat.com/console/ >>> >>> >>> _______________________________________________ >>> Ansible-service-broker mailing list >>> Ansible-service-broker at redhat.com >>> https://www.redhat.com/mailman/listinfo/ansible-service-broker >>> >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From rhallise at redhat.com Wed Sep 20 20:01:33 2017 From: rhallise at redhat.com (Ryan Hallisey) Date: Wed, 20 Sep 2017 16:01:33 -0400 Subject: [Ansible-service-broker] kubernetes playbooks in catasb Message-ID: Folks, The kubernetes playbooks have landed in catasb. This may cause a few new issues to show up when using catasb over the next few days, so keep an eye out. If you want to try out deploying the broker on kubernetes see: https://github.com/fusor/catasb/blob/master/kubernetes/README.md Next, all the broker scripts will be converted to be usable with Kubernetes. That way we'll have the gate testing on kubernetes and running a local broker will work with k8s. Thanks, - Ryan From dymurray at redhat.com Fri Sep 22 19:09:58 2017 From: dymurray at redhat.com (Dylan Murray) Date: Fri, 22 Sep 2017 15:09:58 -0400 Subject: [Ansible-service-broker] APB Versioning Discussion Message-ID: All, I have put together a Google Doc describing a potential versioning system to put into place as we begin our 3.7 release process. Please feel free to add your comments and I will put together a meeting early next week to discuss. Main points: Major vs. Minor version bump Does version match broker/OCP release or is it it's own? https://docs.google.com/a/redhat.com/document/d/1h2PrsL-BRNbey9efh4QJvS0C4Lnq2moeJfYdgF8y070/edit?usp=sharing Thanks, Dylan -------------- next part -------------- An HTML attachment was scrubbed... URL: From shurley at redhat.com Mon Sep 25 12:51:45 2017 From: shurley at redhat.com (Shawn Hurley) Date: Mon, 25 Sep 2017 08:51:45 -0400 Subject: [Ansible-service-broker] Merging Bearer Token Auth Message-ID: <705240ac-7bc3-da63-76f0-90de1898138c@redhat.com> Hello, The Bearer token auth PR should be merging soon (was thinking around noon today) and the corresponding CATASB PR will be merged as well. When this gets merged you will need to update CATASB as the there are template changes being made. This PR also is removing the feature to start the broker in "insecure" mode. This PR also is removing the ASB route, instead, we are using the internal kubernetes DNS and passing that url to the service catalog. I will be doing a follow-on PR that updates the documentation. If anyone has concerns, would like to test, or review you can find the PRs below. ASB PR: https://github.com/openshift/ansible-service-broker/pull/445 CATASB PR: https://github.com/fusor/catasb/pull/142 Thanks, Shawn Hurley From shurley at redhat.com Tue Sep 26 16:49:22 2017 From: shurley at redhat.com (Shawn Hurley) Date: Tue, 26 Sep 2017 12:49:22 -0400 Subject: [Ansible-service-broker] Merging Bearer Token Auth In-Reply-To: <705240ac-7bc3-da63-76f0-90de1898138c@redhat.com> References: <705240ac-7bc3-da63-76f0-90de1898138c@redhat.com> Message-ID: Hello All, I am planning on merging this PR today after the 1pm meeting. There has been a change to this statement: > This PR also is removing the ASB route, instead, we are using the > internal kubernetes DNS and passing that url to the service catalog. We are keeping the route around otherwise apb tool would have issues contacting the broker. We can work on a different approach later if this is important to people. When it merges you will need to update CATASB to use the new template in master. Thanks, Shawn Hurley On 09/25/2017 08:51 AM, Shawn Hurley wrote: > ASB PR: https://github.com/openshift/ansible-service-broker/pull/445 > CATASB PR: https://github.com/fusor/catasb/pull/142 From shurley at redhat.com Tue Sep 26 17:27:19 2017 From: shurley at redhat.com (Shawn Hurley) Date: Tue, 26 Sep 2017 13:27:19 -0400 Subject: [Ansible-service-broker] Merging Bearer Token Auth In-Reply-To: References: <705240ac-7bc3-da63-76f0-90de1898138c@redhat.com> Message-ID: <50e7ec16-be6f-7410-ea56-374eee0cbb8c@redhat.com> The PR has been merged. If anyone sees any issues please let me know Thanks, Shawn Hurley From jmrodri at gmail.com Thu Sep 28 03:53:52 2017 From: jmrodri at gmail.com (Jesus M. Rodriguez) Date: Wed, 27 Sep 2017 23:53:52 -0400 Subject: [Ansible-service-broker] Fwd: Open Service Broker API v2.13 Released In-Reply-To: References: Message-ID: ---------- Forwarded message ---------- From: Matt McNeeney Date: Wed, Sep 27, 2017 at 5:44 AM Subject: Open Service Broker API v2.13 Released To: open-service-broker-api Hello all, Great news - *v2.13 of the Open Service Broker API specification is now live!* This version includes a number of new features, including: - Added a schemas field to services in the catalog that brokers can use to declare the configuration parameters their service accepts for creating a service instance, updating a service instance and creating a service binding. - Added a context field to the request body for creating a service binding. - Allow non-BasicAuth authentication mechanisms . - Added a Getting Started page including sample service brokers. - Add originating identity HTTP header . For more information, please check out the specification and release notes . The roadmap & release planning project has been updated accordingly. A blog post has been published as part of this release which you can find here . Thanks to the group for their hard work getting this release out. Any community feedback on this release from either service broker authors or platform authors would be greatly appreciated. Matt ? -- You received this message because you are subscribed to the Google Groups "open-service-broker-api" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-service-broker-api+unsubscribe at googlegroups.com. To post to this group, send email to open-service-broker-api@ googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/ msgid/open-service-broker-api/CAONPG_w5%2BjENBb4e- KuqYXV8BpDnH1dPs7n-88r6D_k%3DjqUjEQ%40mail.gmail.com . For more options, visit https://groups.google.com/d/optout. -------------- next part -------------- An HTML attachment was scrubbed... URL: