-
Notifications
You must be signed in to change notification settings - Fork 37
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
[DOCS] Document the use of environment variables that may be too sensitive to be kept in YAML #115
Comments
In the absence of these docs I'm trying to figure out how to use My
When I execute the command
You can see it's generating I haven't looked at the broker code yet to figure out what the broker is expecting. Any ideas? |
See cloudfoundry/cloud-service-broker#108 (comment) This isn't working just yet...! See comments here: cloudfoundry/cloud-service-broker#115 (comment) In the meantime, there's an (in-progress) workaround in `make test-eden`.
See cloudfoundry/cloud-service-broker#108 (comment) This isn't working just yet...! See comments here: cloudfoundry/cloud-service-broker#115 (comment) In the meantime, there's an (in-progress) workaround in `make test-eden`.
Here's a clue, from a file that's no longer in the repository: The JSON annotations here should result in those values also being populated from |
This isn't really what the examples section of the brokerpak were built for. To test situations that require sensitive information (especially that will be unique to your environment) we suggest using the |
We inspected the source and finally figured out what the JSON for the |
Did this solve your problem @mogul ? |
Yes it did! I do suggest documenting it. |
See cloudfoundry/cloud-service-broker#108 (comment) This isn't working just yet...! See comments here: cloudfoundry/cloud-service-broker#115 (comment) In the meantime, there's an (in-progress) workaround in `make test-eden`.
A possible workaround: It appears that the
client run-examples
command accepts some parameters:I suspect I can supply the test parameters using the
--filename
parameter, although there's no documentation about this option or what aCompleteServiceExamples
might be. (I am guessing it is expecting a YAML block that corresponds to theexamples
block in the service YAML; will report back.)This needs documentation!
Originally posted by @mogul in https://github.com/pivotal/cloud-service-broker/issue_comments/708887286
The text was updated successfully, but these errors were encountered: