cloudfoundry/notifications-release issues and pull requests

#40 - Fix potential issue with auth calls

Pull Request - State: closed - Opened by reedr3 over 1 year ago

#39 - Allow @ character in uaa secret

Pull Request - State: closed - Opened by nhsieh over 3 years ago - 1 comment

#38 - Use job-level properties instead of top-level

Pull Request - State: closed - Opened by tjvman over 4 years ago - 1 comment

#37 - Request to bump to CF-CLI BOSH Release >= v1.15

Issue - State: closed - Opened by osis about 5 years ago

#36 - Colocate the CF CLI Bosh Release

Issue - State: closed - Opened by osis about 5 years ago - 1 comment

#35 - Add better stdout messages during errand rerunning

Pull Request - State: closed - Opened by gmrodgers about 5 years ago - 2 comments
Labels: accepted

#34 - Check if deploy errand is colocated; if yes then run else use original logic

Pull Request - State: closed - Opened by terminatingcode over 5 years ago - 2 comments
Labels: accepted

#33 - Spin wait for the API endpoint to become available

Pull Request - State: closed - Opened by oozie over 5 years ago - 3 comments
Labels: accepted

#32 - Repush notifications app in bbr `post-restore-unlock` script

Pull Request - State: closed - Opened by ChunyiLyu over 5 years ago - 5 comments
Labels: accepted

#31 - `notifications.database.common_name` should not be a required field

Issue - State: open - Opened by ljfranklin over 5 years ago - 1 comment
Labels: unscheduled

#30 - Use colocated cf-cli-release

Pull Request - State: closed - Opened by davewalter almost 6 years ago - 2 comments
Labels: accepted

#29 - Detect which stack (cflinuxfs2 or cflinuxfs3) to use at runtime

Pull Request - State: closed - Opened by davewalter almost 6 years ago - 2 comments
Labels: accepted

#28 - Don't print out password

Pull Request - State: closed - Opened by alamages about 6 years ago - 3 comments
Labels: accepted

#27 - Change database link so it can consume cf-mysql-release

Pull Request - State: closed - Opened by oppegard about 6 years ago - 5 comments
Labels: accepted

#26 - notifications fails to start

Issue - State: closed - Opened by trevorwhitney over 6 years ago - 6 comments
Labels: accepted

#25 - restore-lock scripts should not run if notifications not deployed

Pull Request - State: closed - Opened by tinygrasshopper over 6 years ago - 3 comments
Labels: accepted

#24 - Set CF_HOME to a temp dir to a avoid bug in autopilot

Pull Request - State: closed - Opened by davewalter over 6 years ago - 3 comments
Labels: accepted

#23 - Update backup-restore-notifications to consume a database link

Pull Request - State: closed - Opened by davewalter over 6 years ago - 4 comments

#22 - Update BBR jobs to consume settings via link from deploy-notifications

Pull Request - State: closed - Opened by utako over 6 years ago - 4 comments

#21 - Namespace the packages used the the errand jobs

Pull Request - State: closed - Opened by ryanmoran over 6 years ago - 3 comments
Labels: unscheduled

#20 - Add metadata script for locking order

Pull Request - State: closed - Opened by ChunyiLyu over 6 years ago - 4 comments
Labels: accepted

#19 - Manifest problems

Issue - State: open - Opened by henryaj over 6 years ago - 2 comments
Labels: unscheduled

#18 - create LICENSE and NOTICE

Pull Request - State: closed - Opened by christopherclark about 7 years ago - 2 comments
Labels: unscheduled

#17 - Blue-green deploy failure doesn't capture any logs

Issue - State: open - Opened by dprotaso about 7 years ago - 1 comment
Labels: unscheduled

#16 - Deploy errand will fail when reusing a vm using --keep-alive

Issue - State: open - Opened by dprotaso about 7 years ago - 1 comment
Labels: unscheduled

#15 - deploy-notifications can find database address from a link

Pull Request - State: closed - Opened by wendorf about 7 years ago - 2 comments
Labels: accepted

#14 - Database URL can be specified by component pieces in job spec

Pull Request - State: closed - Opened by wendorf about 7 years ago - 3 comments
Labels: accepted

#13 - Go release version not correct

Issue - State: closed - Opened by mosesliao over 7 years ago - 1 comment

#12 - Can this release use a MySQL service broker in a spinning Cloud Foundry?

Issue - State: closed - Opened by jhunt over 7 years ago - 1 comment

#11 - remove diego config from bosh property

Pull Request - State: closed - Opened by jtarchie almost 8 years ago - 1 comment

#10 - go version on release not correct

Issue - State: closed - Opened by vfonsecapv about 8 years ago - 1 comment

#9 - Update .gitmodules

Pull Request - State: closed - Opened by sks about 8 years ago - 1 comment

#8 - Error when deploy-notifications

Issue - State: closed - Opened by vfonsecapv about 8 years ago

#7 - Offer vsphere / vcloud / openstack manifest templates

Issue - State: closed - Opened by poblin-orange over 8 years ago

#6 - Changes xip.io address to bosh-lite.com

Pull Request - State: closed - Opened by tjvman over 8 years ago - 2 comments

#5 - Add buildpack_url parameter, for environments that might not be running the latest go buildpack

Pull Request - State: closed - Opened by jrbudnack over 8 years ago - 3 comments

#4 - Ensure that manifest.yml uses the app_domain property instead of the system domain to deploy the notifications app to CF

Pull Request - State: closed - Opened by jrbudnack over 8 years ago - 2 comments

GitHub / cloudfoundry/notifications-release issues and pull requests