Separate JD database

[skudasov]

---

Below is a summarization created by an LLM (gpt-4-0125-preview). Be mindful of hallucinations and verify accuracy.

Why

The changes enhance the JobDistributor (JD) component and its integration with the PostgreSQL database, improving the testing framework by allowing more dynamic configuration and interaction. Specifically, separating the JD database setup into its configuration allows for more flexibility and better encapsulation of database specifics. Additionally, ensuring transactions are mined before proceeding enhances reliability during testing on testnets by confirming state changes are complete.

What

• framework/.changeset/v0.3.7.md
  • Added a changeset file for version 0.3.7 including separate JobDistributor database setup and modification to wait for fund transactions to be mined on testnets.
• framework/components/jd/jd.go
  • Imported the postgres component for database interactions.
  • Removed DBURL from Input struct and added DBInput for direct postgres configuration.
  • Added a default postgres database configuration specific to JD (defaultJDDB function).
  • Integrated the new postgres setup in NewJD function, using DBInput for database configuration.
• framework/components/jd/jd_test.go
  • Removed direct PostgreSQL setup, relying on jd.NewJD to handle its database integration.
• framework/components/postgres/postgres.go
  • Added Name and JDDatabase fields in Input struct for customizable container names and enabling a specific database setup for JD.
  • Adjusted container naming and database setup logic to accommodate the new fields.
  • Modified the database URL construction to conditionally include JD database URLs based on the new input.
• framework/components/simple_node_set/fund.go
  • Added a call to bind.WaitMined to wait for the transaction to be mined, improving reliability in testing environments.
• framework/examples/myproject_cll/jd_test.go
  • Removed setting DBURL directly in test setup, relying on the updated JD component configuration.

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube