GraphQL schema are generated dynamically, on configuration, as a convenience in order to distinguish schema for key authentication (non-nullable input field 'key') and JWT token (no such field). It is preferable to generate schema statically, during installation of the debian package vyos-1x, as one can then apply code generation tools for client types and operations. Consequently, use nullable field 'key' and generate schema in vyos-1x.postinst.
Description
Description
Details
Details
- Version
- vyos-1.4
- Is it a breaking change?
- Perfectly compatible
- Issue type
- Internal change (not visible to end users)
Related Objects
Related Objects
- Mentioned In
- rVYOSONEX3204cdb1f92b: graphql: T5040: use nullable key field to allow schema static generation
rVYOSONEXee95772c8e72: graphql: T5040: fail gracefully if not on live system; needed for import
rVYOSONEX57ca4de21602: graphql: T5040: generate schema in vyos-1x.postinst
rVYOSONEXbabff628aa9a: graphql: T5040: adjust smoketest for nullable key
rVYOSONEX7ab3b9e021e7: graphql: T5040: use path from defaults
rVYOSONEX493af3f3417c: Merge pull request #1862 from jestabro/schema-generate