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
@yudai Newer versions of cf-release (238, 239, etc.) include pre-start scripts in their jobs. In many cases, these scripts create directories for use in the actual jobs. The existing cf_nise_installer does not invoke these and as a result these jobs in these releases will not work. I note mention of support for pre-start scripts added here: https://bosh.io/docs/pre-start.html
Do you have intention of updating nise_bosh and cf_nise_installer to a newer level to include support for items such as pre-start scripts?
The text was updated successfully, but these errors were encountered:
I also find that the newer levels of cf-release use the property spec.bootstrap as a boolean. This property is used in both the pre-start and post-start scripts of the cloud_controller_ng job. In the pre-start case this value gates logic used to migrate the CCDB to the latest level. In the post-start script, this value gates logic to populate buildpacks. Since the spec.bootstrap value is not supported in the current cf_nise_installer, neither the CCDB migration nor the buildpack population gets done.
@yudai Newer versions of cf-release (238, 239, etc.) include pre-start scripts in their jobs. In many cases, these scripts create directories for use in the actual jobs. The existing cf_nise_installer does not invoke these and as a result these jobs in these releases will not work. I note mention of support for pre-start scripts added here: https://bosh.io/docs/pre-start.html
Do you have intention of updating nise_bosh and cf_nise_installer to a newer level to include support for items such as pre-start scripts?
The text was updated successfully, but these errors were encountered: