You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It has been brought up that it would be useful for a developer to be able to know what credentials are exposed in bindable applications without looking deep into the provision role. Ideally these values would be displayed to the end user in the service catalog so that a developer knows how to consume the APB. This could be a new field on apb.yml.
The text was updated successfully, but these errors were encountered:
On Fri, Jan 19, 2018 at 10:10 AM, Dylan Murray ***@***.***> wrote:
It has been brought up that it would be useful for a developer to be able
to know what credentials are exposed in bindable applications without
looking deep into the provision role. Ideally these values would be
displayed to the end user in the service catalog so that a developer knows
how to consume the APB. This could be a new field on apb.yml.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#206>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACAZidsd2hHv1x0ZEtT81icGHVb_4h0-ks5tMLBrgaJpZM4Rkm9y>
.
--
Todd Sanders
Director, Software Engineering
Red Hat Inc.
Would this be only for the keys, for example DB_USER, DB_PASSWORD, and not the values of those keys? I just want to make sure I'm understanding what your definition of values is.
It has been brought up that it would be useful for a developer to be able to know what credentials are exposed in bindable applications without looking deep into the provision role. Ideally these values would be displayed to the end user in the service catalog so that a developer knows how to consume the APB. This could be a new field on
apb.yml
.The text was updated successfully, but these errors were encountered: