Add the ability to use TLS to the redis-session extension

[atgitwk]

Hello,
PHP buildpack does not seem to support the automatic setting of php ini session_save_path variable for redis-sessions services with TLS.
extensions/sessions/extension.py only handles the 'tcp:' scheme.

    def session_save_path(self):
        return "tcp://%s:%s?auth=%s" % (
            self.creds.get('hostname',
                           self.creds.get('host', 'not-found')),
            self.creds.get('port', 'not-found'),
            self.creds.get('password', ''))

To use TLS, the Redis 'uri' specification indicates that the ‘uri’ parameter could be set with scheme ‘rediss://’ instead of ‘redis://’.
This 'uri' parameter could be initialized in the json binding credentials configuration provided by the service broker.
Here's a proposal PR for managing redis-session with TLS

• I have viewed signed and have submitted the Contributor License Agreement
  Go an error at link Individual CLA : Error 404 Not Found 😟

• I have made this pull request to the master branch

• I have added an integration test

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: atgitwk / name: Antonio Torres (3b19b4f, 9de2b30)

[atgitwk]

Hi team
My PR is still in pending review but cloudfoundry/wg-app-runtime-interfaces-buildpacks-php-approvers returns HTTP 404 "Page not found" 😞
Is this normal ?
May anyone help ?

[ramonskie]

hi sorry for the delay. allot of happend in the past few months.

• moving pipelines for the buildpacks
• changing teams
• complete refactor of the php buildpack see Complete Go migration: Remove Python infrastructure and add comprehensive test suite #1203

i would kindly ask if you could create a new pr for the new buildpack. as this is now rewriten in go
and as soon as i see your new pr we will review and merge it
let me know if you need any more information

[atgitwk]

Hi @ramonskie
I have updated my forked version with the major version 5.x.x and added the proposed solution but in Go now.
Is it ok ?

[atgitwk]

Thanks, @ramonskie.
It may be implemented in the next release ? Any date ?