-
Notifications
You must be signed in to change notification settings - Fork 133
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
MySQL Instance fills out endpoint field in ConnectionSecret in an unexpected way, breaking crossplane-contrib/sql-provider #778
Comments
Previously the ConnectionSecret endpoint field contained the hostname including the port. This is not expected behaviour and makes the ConnectionSecret unuseable by downstream consumers of the Secret, like https://github.com/crossplane-contrib/provider-sql, which expected the endpoint and port to be in seperate fields. Fixes: crossplane-contrib#778
Previously the ConnectionSecret endpoint field contained the hostname including the port. This is not expected behaviour and makes the ConnectionSecret unuseable by downstream consumers of the Secret, like https://github.com/crossplane-contrib/provider-sql, which expected the endpoint and port to be in seperate fields. Fixes: crossplane-contrib#778
Previously the ConnectionSecret endpoint field contained the hostname including the port. This is not expected behavior and makes the ConnectionSecret unusable by downstream consumers of the Secret, like https://github.com/crossplane-contrib/provider-sql, which expect the endpoint and port to be in separate fields. Fixes: crossplane-contrib#778
Previously the ConnectionSecret endpoint field contained the hostname including the port. This is not expected behavior and makes the ConnectionSecret unusable by downstream consumers of the Secret, like https://github.com/crossplane-contrib/provider-sql, which expect the endpoint and port to be in separate fields. Fixes: crossplane-contrib#778 Signed-off-by: Benjamin Ritter <[email protected]>
Hi! I have same problem with postgresql ads instance. Any updates? |
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as |
/fresh |
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as |
/fresh |
/fresh again |
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as |
/fresh again and again |
FYI #1578 |
What happened?
When using the rds.aws.upbound.io/v1beta1/Instance Resource to create a database and writing the credentials to a connectionSecret the endpoint field unexpectedly includes a port in the endpoint field. This breaks compatibility with the https://github.com/crossplane-contrib/provider-sql Provider, due to it not supporting to use another field for its endpoint reference.
How can we reproduce it?
What environment did it happen in?
The text was updated successfully, but these errors were encountered: