nfsbrokerpush job from nfs-volume/1.3.0
              Github source:
              77c98d2 or
              master branch
            
Properties¶
nfsbrokerpush¶
  
  
    
app_domain¶domain used to host the broker app
app_name¶application name to use when pushing the broker to cloud foundry and setting the route
- Default
nfsbroker
cf¶
admin_password¶password of the CF admin user
admin_user¶username of the CF admin user
dial_timeout¶CF CLI connection dial timeout
- Default
5
create_sql_security_group¶true if the errand should create a security group to allow traffic to any ip on ports 3306,5432
- Default
true
db¶
driver¶mysql or postgres
- Default
mysql
host¶database host
name¶database name
password¶database password
port¶database port
- Default
3306
username¶database username
domain¶Cloud Foundry system domain
error_on_misconfiguration¶throw error on service misconfiguration during deployment
- Default
true
ldap_enabled¶true if the broker should use ldap username/password bind config instead of uid/gid
- Default
false
ldap_test_mode¶true if the broker should allow either ldap username/password bind config or uid/gid
- Default
false
memory_in_mb¶amount of memory allocated to the broker app
- Default
256
organization¶organization that hosts the app
password¶service broker password
register_broker¶true if the errand should register the service broker after pushing it to cf
- Default
true
service_name¶service name in marketplace
- Default
nfs
skip_cert_verify¶true if the cf api uses test certs that should not be verified
- Default
false
space¶space that hosts the app
syslog_url¶external log service URL
username¶service broker username
Templates¶
            Templates are rendered and placed onto corresponding
            instances during the deployment process. This job's templates
            will be placed into /var/vcap/jobs/nfsbrokerpush/ directory
            (learn more).
          
- bin/run(from- deploy.sh.erb)
- manifest.yml(from- manifest.yml.erb)
- sql.json(from- sql.json.erb)
Packages¶
            Packages are compiled and placed onto corresponding
            instances during the deployment process. Packages will be
            placed into /var/vcap/packages/ directory.