Skip to content

[Messenger] Add rediss:// DSN scheme support for TLS to Redis transport #39607

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

Merged
merged 1 commit into from
Feb 26, 2021

Conversation

njutn95
Copy link
Contributor

@njutn95 njutn95 commented Dec 22, 2020

Q A
Branch? 5.x
Bug fix? no
New feature? no
Deprecations? yes
Tickets
License MIT
Doc PR

This adds a support for rediss:// DSN (as discussed in #39599) and deprecates the use of tls parameter introduced in #35503 so it can be standardized to single format.

Copy link
Member

@jderusse jderusse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As said in #39599 (comment) we should not support 2 ways to define the same thing (?tls=true vs rediss://)
This could lead to inconsistency like rediss://localhost?tls=false ?

@njutn95
Copy link
Contributor Author

njutn95 commented Dec 22, 2020

I agree. Lets see first which should be considered a "primary" one, so that the other one can be deprecated/removed. However, both rediss:// and tls:// are used somewhat equally, rediss:// being somewhat a better choice in case of Redis Cache Adapter where the adapter is actually being recognized based on the DSN.

@nicolas-grekas nicolas-grekas added this to the 5.x milestone Dec 23, 2020
@njutn95 njutn95 force-pushed the feature/messenger-redis-tls branch from 592d0fd to 464f747 Compare December 24, 2020 10:27
@njutn95 njutn95 changed the title [Messenger] Add TLS alternative to Redis transport's DSN with rediss:// scheme [Messenger] Add rediss:// DSN scheme support for TLS to Redis transport Dec 24, 2020
@OskarStark
Copy link
Contributor

OskarStark commented Feb 1, 2021

Can you please rebase to get rid of the conflicts? Thanks

@njutn95 njutn95 force-pushed the feature/messenger-redis-tls branch from c7508fe to 3f19c28 Compare February 1, 2021 08:50
@njutn95
Copy link
Contributor Author

njutn95 commented Feb 1, 2021

@OskarStark Done

@nicolas-grekas nicolas-grekas modified the milestones: 5.x, 4.4 Feb 22, 2021
Copy link
Member

@nicolas-grekas nicolas-grekas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(with minor comments)

@njutn95 njutn95 force-pushed the feature/messenger-redis-tls branch from 3f19c28 to 89c4308 Compare February 25, 2021 21:50
@nicolas-grekas nicolas-grekas modified the milestones: 4.4, 5.x Feb 25, 2021
@nicolas-grekas nicolas-grekas force-pushed the feature/messenger-redis-tls branch from dd83644 to 28e7b74 Compare February 26, 2021 00:02
@nicolas-grekas
Copy link
Member

Thank you @njutn95.

@nicolas-grekas nicolas-grekas merged commit 59fbe57 into symfony:5.x Feb 26, 2021
@fabpot fabpot mentioned this pull request Apr 18, 2021
nicolas-grekas added a commit that referenced this pull request Sep 8, 2021
…cky)

This PR was submitted for the 5.4 branch but it was squashed and merged into the 5.3 branch instead.

Discussion
----------

[Messenger] Support rediss in transport bridge

| Q             | A
| ------------- | ---
| Branch?       | 5.3
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Tickets       | -
| License       | MIT
| Doc PR        |

Seems like support for `rediss` was added in the [main package](https://github.com/symfony/symfony/blob/e34cd7dd2c6d0b30d24cad443b8f964daa841d71/src/Symfony/Component/Messenger/Transport/TransportFactory.php#L46), but didn't propagate to the bridge

Followed a trail from here - #39607

Commits
-------

edfad64 [Messenger] Support rediss in transport bridge
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants