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
Copy file name to clipboardexpand all lines: README.md
+6-1
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,11 @@
21
21
22
22
WunderGraph Cosmo is a comprehensive Lifecycle API Management platform tailored for Federated GraphQL. It encompasses everything from Schema Registry, composition checks, and analytics, to metrics, tracing, and routing. Whether you’re looking to deploy 100% on-prem or prefer a [Managed Service](https://cosmo.wundergraph.com/login), Cosmo offers flexibility without vendor lock-in, all under the Apache 2.0 license.
23
23
24
+
## The State of GraphQL Federation 2024
25
+
26
+
Get insights from industry experts and Federation practicioners across all industries and learn how companies are using GraphQL Federation.
27
+
Head over to the [State of GraphQL Federation 2024](https://wundergraph.com/state-of-graphql-federation/2024) page and download the full **48 page PDF report** for free!
28
+
24
29
### Why Federated GraphQL?
25
30
26
31
GraphQL Federation empowers organizations to break down their GraphQL schema into multiple smaller, manageable schemas, each maintained by different teams or services. These individual schemas are then combined into a single, unified graph, ensuring that all teams have consistent access to the data they need. In today's data-driven world, where information is often referred to as the new oil, building a unified API that can be consumed by both internal and external teams is more crucial than ever.
@@ -74,4 +79,4 @@ We welcome contributions from the community! Whether it's fixing a bug, adding n
74
79
75
80
## License
76
81
77
-
Cosmo is licensed under the [Apache License, Version 2.0](LICENSE).
82
+
Cosmo is licensed under the [Apache License, Version 2.0](LICENSE).
* composition warnings should respect --json flag and output in JSON format ([#1673](https://github.com/wundergraph/cosmo/issues/1673)) ([745140f](https://github.com/wundergraph/cosmo/commit/745140f001230fea2cbd1fd7e6e2b12d47eeb36f)) (@JivusAyrus)
message: `Feature subgraph was published, but the updated composition hasn't been deployed, so it's not accessible to the router. Check the errors listed below for details.`,
"Feature subgraph was published, but the updated composition hasn't been deployed, so it's not accessible to the router. Check the errors listed below for details.",
194
-
);
195
-
196
-
constdeploymentErrorsTable=newTable({
197
-
head: [
198
-
pc.bold(pc.white('FEDERATED_GRAPH_NAME')),
199
-
pc.bold(pc.white('NAMESPACE')),
200
-
pc.bold(pc.white('ERROR_MESSAGE')),
201
-
],
202
-
colWidths: [30,30,120],
203
-
wordWrap: true,
204
-
});
205
-
206
-
for(constdeploymentErrorofresp.deploymentErrors){
207
-
deploymentErrorsTable.push([
208
-
deploymentError.federatedGraphName,
209
-
deploymentError.namespace,
210
-
deploymentError.message,
211
-
]);
212
-
}
213
-
// Don't exit here with 1 because the change was still applied
214
-
console.log(deploymentErrorsTable.toString());
215
-
216
-
if(options.failOnAdmissionWebhookError){
217
-
program.error(pc.red(pc.bold('The command failed due to admission webhook errors.')));
resp?.hasChanged===false ? 'No new changes to publish.' : 'Feature subgraph published successfully.',
129
+
subgraphCompositionBaseErrorMessage: 'Feature subgraph published but with composition errors.',
130
+
subgraphCompositionDetailedErrorMessage: `We found composition errors, while composing the federated graph.\nThe router will continue to work with the latest valid schema.\n${pc.bold(
131
+
'Please check the errors below:',
132
+
)}`,
133
+
deploymentErrorMessage: `Feature subgraph was published, but the updated composition hasn't been deployed, so it's not accessible to the router. Check the errors listed below for details.`,
134
+
defaultErrorMessage: `Failed to publish feature subgraph "${name}".`,
0 commit comments