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
Currently, rds.aws.crossplane.io/v1alpha1/DBParameterGroup mirrors the behaviour of the AWS API by requiring dbParameterGroupFamily as input from the user.
However, determining the actual name from the engine and engineVersion parameters can be very cumbersome in a composition. It is made even harder by the inconsistency of the AWS API:
for SQL Server 15.00.4198.2.v1 the group family is sqlserver-se-15.0 missing the additional 0
for Oracle 12.1.0.2.v1 its oracle-ee-12.1, but for 19.0.0.0.ru-2019-07.rur-2019-07.r1 its just oracle-ee-19 missing the minor version.
The list goes on.
How could Crossplane help solve your problem?
Instead of letting the user / composition writer deal with this problem, the provider should offer a shortcut by determining the group family by himself:
Make spec.forProvider.dbParameterGroupFamily optional
What problem are you facing?
Currently,
rds.aws.crossplane.io/v1alpha1/DBParameterGroup
mirrors the behaviour of the AWS API by requiringdbParameterGroupFamily
as input from the user.However, determining the actual name from the
engine
andengineVersion
parameters can be very cumbersome in a composition. It is made even harder by the inconsistency of the AWS API:15.00.4198.2.v1
the group family issqlserver-se-15.0
missing the additional0
12.1.0.2.v1
itsoracle-ee-12.1
, but for19.0.0.0.ru-2019-07.rur-2019-07.r1
its justoracle-ee-19
missing the minor version.The list goes on.
How could Crossplane help solve your problem?
Instead of letting the user / composition writer deal with this problem, the provider should offer a shortcut by determining the group family by himself:
spec.forProvider.dbParameterGroupFamily
optionaldbParameterGroupFamilyFromEngine
dbParameterGroupFamily
is not set the provider should takedbParameterGroupFamilyFromEngine
and get the family name usingdbParameterGroupFamilyFromEngine.engineVersion
is not set, the provider should use the family of the default version by callingThe text was updated successfully, but these errors were encountered: