The GitHub Actions job "End to End" on grails-core.git/feature/mongodb-embedded-8.0.x has succeeded. Run started by GitHub user codeconsole (triggered by codeconsole).
Head commit for run: 905964362bed3e1ba215db3b5abe24682a198a3c / Scott Murphy Heiberg <[email protected]> Ask for an embedded MongoDB by url, the way an in-memory SQL database is asked for An application said where its MongoDB was and then, separately, that it wanted an embedded one, and the second quietly overruled the first. Two properties had to agree about one decision, and when they disagreed the url was the one ignored -- so a url that could not be read was not read as a mistake, it was not read at all, and what failed instead was the datastore several hundred milliseconds later, naming a property nobody had touched. An in-memory SQL database is not configured this way. There is no h2.enabled; h2 sits on the classpath in every environment and the url decides, so development names an in-memory database, production names a server, and an application with a PostgreSQL url never starts H2 no matter what is on its classpath. An embedded MongoDB is asked for the same way now. Where an application would name a host it names embedded instead, optionally with a port: environments: development: grails: mongodb: url: mongodb://embedded/bookstore production: grails: mongodb: url: mongodb://localhost:27017/bookstore Nothing else switches it on and nothing switches it off. embedded.mongodb's enabled, port and database are gone: the first is the url naming embedded, and the other two are what a url has always been able to say. What is left configures the server behind that url -- which backend, which version, whether it keeps its data -- rather than which server to reach. A host genuinely named embedded can no longer be reached through these properties, and is named by address or fully qualified name instead. Report URL: https://github.com/apache/grails-core/actions/runs/31280703671 With regards, GitHub Actions via GitBox
