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
Most Vultr Managed Databases options return GO errors during execution. In particular, most options return errors when executed while database-specific commands such as vultr-cli database list, vultr-cli database get , vultr-cli database db list work without issues.
To Reproduce
Steps to reproduce the behavior:
Enter a Vultr Managed Databases command such as vultr-cli database plan list
See the error in your output similar to the one below.
Expected behavior
Expected to receive plan information. Tried other options as well apart from the plan, and received similar errors. In particular, when querying and creating PostgreSQL clusters. For example:
vultr-cli database create --database-engine pg --database-engine-version 17 --plan vultr-dbaas-hobbyist-cc-1-25-1 --region ewr --label "testdb"
Error: error creating database : json: cannot unmarshal object into Go struct field Database.database.trusted_ips of type []string
The text was updated successfully, but these errors were encountered:
@mjhumphrey4 This could be a result of not having recently released code changes since I'm not seeing these errors on master. I'm going to push through a new release this week and would appreciate it if you could test it on the new release.
Describe the bug
Most Vultr Managed Databases options return GO errors during execution. In particular, most options return errors when executed while database-specific commands such as
vultr-cli database list
,vultr-cli database get
,vultr-cli database db list
work without issues.To Reproduce
Steps to reproduce the behavior:
vultr-cli database plan list
Expected behavior
Expected to receive plan information. Tried other options as well apart from the plan, and received similar errors. In particular, when querying and creating PostgreSQL clusters. For example:
The text was updated successfully, but these errors were encountered: