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
If you have to use a Postgres image that is not directly supported by the PostgresqlContainer class you've got quite an issue. With the bitnami postgres image for instance you don't want a command to be set during container creation. As this is done in the constructor of the class and the setCommand() method does not allow for null values you end up creating a copy of the PostgresqlContainer class just to get rid of the command.
I think there are a number of things that could be done about it.:
provide another PostgresContainer class that does not set a command
make the setCommand() method nullable
provide an alternative constructor for the PostgresqlContainer class
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all,
If you have to use a Postgres image that is not directly supported by the PostgresqlContainer class you've got quite an issue. With the bitnami postgres image for instance you don't want a command to be set during container creation. As this is done in the constructor of the class and the setCommand() method does not allow for null values you end up creating a copy of the PostgresqlContainer class just to get rid of the command.
I think there are a number of things that could be done about it.:
What do you think about it?
Best regards
Jan
Beta Was this translation helpful? Give feedback.
All reactions