3ecfa2c726
This adds a check in the route specs that TYPE_ETC ubid values are not present in responses. It then changes four models to use model-specific ubid types instead of TYPE_ETC. The original impetus for this change is to eventually remove authorization code that explicitly checks for TYPE_ETC and assumes ApiKey, which will cause problems in the future if we ever have another model using TYPE_ETC that the authorization system needs to deal with.
19 lines
493 B
Plaintext
19 lines
493 B
Plaintext
id: pgvm1qb9gwct1mqmay7m54yma5
|
|
name: test-pg
|
|
state: creating
|
|
location: eu-central-h1
|
|
vm_size: standard-2
|
|
storage_size_gib: 64
|
|
version: 16
|
|
ha_type: none
|
|
flavor: standard
|
|
connection_string: postgres://postgres:bar456FOO123@test-pg.pgvm1qb9gwct1mqmay7m54yma5.pg.example.com?channel_binding=require
|
|
primary: true
|
|
earliest_restore_time:
|
|
firewall rules:
|
|
1: pfb9g14e5ndt6qf59wfk8109bg 0.0.0.0/0
|
|
metric destinations:
|
|
1: md8ntmx8e1764nwc7p970vf3xw foo https://baz.example.com
|
|
CA certificates:
|
|
|