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
IMHO Cadence domain is analogue of a database. Most official database images offer an option (usually an environment variable) to create a domain when the container is first started. This is mostly useful in development environments to avoid manual steps in the quick setup guide.
Something similar would be nice in case of Cadence as well.
Currently the only problem I see is there is no state in the container (which is not a problem per se), but there is no way to track whether the domain is created or not, other than in the cassandra database of course. However, there is no "ensure" option in the cadence CLI. So if the domain creation fails, where is no way to tell if it is because the domain already exists or for some other reason.
A possible solution would be adding an "ensure" command in the cadence CLI that creates the domain in an idempotent way (if necessary).
The text was updated successfully, but these errors were encountered:
IMHO Cadence domain is analogue of a database. Most official database images offer an option (usually an environment variable) to create a domain when the container is first started. This is mostly useful in development environments to avoid manual steps in the quick setup guide.
Something similar would be nice in case of Cadence as well.
Currently the only problem I see is there is no state in the container (which is not a problem per se), but there is no way to track whether the domain is created or not, other than in the cassandra database of course. However, there is no "ensure" option in the cadence CLI. So if the domain creation fails, where is no way to tell if it is because the domain already exists or for some other reason.
A possible solution would be adding an "ensure" command in the cadence CLI that creates the domain in an idempotent way (if necessary).
The text was updated successfully, but these errors were encountered: