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
#41 adds board support for creating, updating, and deleting Kubernetes resources via xgql. I believe this technically covers all our use cases and is in some cases the best we can really do - e.g. for types like XRs and managed resources where we don't know the full schema of the resource.
There are however some mutations for well known resources - e.g. installing a provider or a configuration - that will be common and where we do know the schema. It would be ideal if we had 'strongly typed'/'structured' mutations for these types.
How could xgql help solve your problem?
xgql could add structured mutations for well-known types, particularly creating and updating configurations, and providers. At some point we may also want to support working with XRDs and Compositions directly.
The text was updated successfully, but these errors were encountered:
What problem are you facing?
#41 adds board support for creating, updating, and deleting Kubernetes resources via xgql. I believe this technically covers all our use cases and is in some cases the best we can really do - e.g. for types like XRs and managed resources where we don't know the full schema of the resource.
There are however some mutations for well known resources - e.g. installing a provider or a configuration - that will be common and where we do know the schema. It would be ideal if we had 'strongly typed'/'structured' mutations for these types.
How could xgql help solve your problem?
xgql could add structured mutations for well-known types, particularly creating and updating configurations, and providers. At some point we may also want to support working with XRDs and Compositions directly.
The text was updated successfully, but these errors were encountered: