diff --git a/changelog/v1.18.0-beta12/remove-unneeded-cat.yaml b/changelog/v1.18.0-beta12/remove-unneeded-cat.yaml new file mode 100644 index 00000000000..683c3335dfb --- /dev/null +++ b/changelog/v1.18.0-beta12/remove-unneeded-cat.yaml @@ -0,0 +1,6 @@ +changelog: + - type: NON_USER_FACING + description: >- + Remove unneeded cat calls from our docs + + skipCI-kube-tests:true diff --git a/docs/content/guides/dev/example-proxy-controller.txt b/docs/content/guides/dev/example-proxy-controller.txt index 6690dac6f93..fc86de90fc7 100644 --- a/docs/content/guides/dev/example-proxy-controller.txt +++ b/docs/content/guides/dev/example-proxy-controller.txt @@ -892,7 +892,7 @@ the configmap you'll need: ```bash -cat << EOF | kubectl apply -f - +kubectl apply -f - << EOF apiVersion: v1 kind: ConfigMap metadata: @@ -957,7 +957,7 @@ if you're using a Kubernetes Cluster without an external load balancer (e.g. min Run the following command to create the service: ```bash -cat << EOF | kubectl apply -f - +kubectl apply -f - << EOF apiVersion: v1 kind: Service metadata: @@ -980,7 +980,7 @@ EOF Finally we'll want to create the deployment itself which will launch a pod with Envoy running inside. ```bash -cat << EOF | kubectl apply -f - +kubectl apply -f - << EOF apiVersion: apps/v1 kind: Deployment metadata: @@ -1150,4 +1150,4 @@ returns [{"id":1,"name":"Dog","status":"available"},{"id":2,"name":"Cat","status":"pending"}] ``` -Nice. You've configured Gloo Gateway to proactively create routes to discovered consul services! \ No newline at end of file +Nice. You've configured Gloo Gateway to proactively create routes to discovered consul services! diff --git a/docs/content/guides/graphql/getting_started/local_executor.md b/docs/content/guides/graphql/getting_started/local_executor.md index 0d8e9742816..779df9fafa0 100644 --- a/docs/content/guides/graphql/getting_started/local_executor.md +++ b/docs/content/guides/graphql/getting_started/local_executor.md @@ -73,7 +73,7 @@ Note that this example uses _local execution_, which means the Envoy server exec 5. Update the `default` virtual service that you previously created to route traffic to `/graphql` to the new `bookinfo-graphql` GraphQL API. {{< highlight yaml "hl_lines=12-16" >}} -cat << EOF | kubectl apply -f - +kubectl apply -f - << EOF apiVersion: gateway.solo.io/v1 kind: VirtualService metadata: diff --git a/docs/content/guides/graphql/getting_started/remote_executor.md b/docs/content/guides/graphql/getting_started/remote_executor.md index a5600834fd8..7921c9ef63a 100644 --- a/docs/content/guides/graphql/getting_started/remote_executor.md +++ b/docs/content/guides/graphql/getting_started/remote_executor.md @@ -70,7 +70,7 @@ In the previous section, you used local execution to resolve GraphQL queries to 4. Update the `default` virtual service that you previously created to route traffic to `/graphql` to the new `default-todos-80` GraphQL API. {{< highlight yaml "hl_lines=12-16" >}} -cat << EOF | kubectl apply -f - +kubectl apply -f - << EOF apiVersion: gateway.solo.io/v1 kind: VirtualService metadata: @@ -108,4 +108,4 @@ EOF curl -X POST -d '{"query":"{todoList{id,text,done}}"}' "$(glooctl proxy url)/graphql" ``` -**Up next**: [Protect the GraphQL API that you created in the previous sections by using an API key.]({{% versioned_link_path fromRoot="/guides/graphql/getting_started/secure_api" %}}) \ No newline at end of file +**Up next**: [Protect the GraphQL API that you created in the previous sections by using an API key.]({{% versioned_link_path fromRoot="/guides/graphql/getting_started/secure_api" %}}) diff --git a/docs/content/guides/graphql/getting_started/secure_api.md b/docs/content/guides/graphql/getting_started/secure_api.md index ec9bce10ff8..caf817689b3 100644 --- a/docs/content/guides/graphql/getting_started/secure_api.md +++ b/docs/content/guides/graphql/getting_started/secure_api.md @@ -37,7 +37,7 @@ Protect the GraphQL API that you created in the previous sections by using an AP 4. Update the `default` virtual service that you previously created to reference the `apikey-auth` AuthConfig. {{< highlight yaml "hl_lines=17-21" >}} -cat << EOF | kubectl apply -f - +kubectl apply -f - << EOF apiVersion: gateway.solo.io/v1 kind: VirtualService metadata: @@ -83,4 +83,4 @@ Now that you've tried out GraphQL with Gloo Gateway, check out the following pag * [Manually configure resolvers and schema for your GraphQL API]({{% versioned_link_path fromRoot="/guides/graphql/resolver_config/" %}}) * [Stitch GraphQL schemas]({{% versioned_link_path fromRoot="/guides/graphql/stitching/" %}}) * [Monitor your GraphQL services]({{% versioned_link_path fromRoot="/guides/graphql/observability/" %}}) -* [Gloo Gateway API reference for GraphQL]({{% versioned_link_path fromRoot="/reference/api/github.com/solo-io/gloo/projects/gloo/api/v1/enterprise/options/graphql/v1beta1/graphql.proto.sk/" %}}) \ No newline at end of file +* [Gloo Gateway API reference for GraphQL]({{% versioned_link_path fromRoot="/reference/api/github.com/solo-io/gloo/projects/gloo/api/v1/enterprise/options/graphql/v1beta1/graphql.proto.sk/" %}}) diff --git a/docs/content/guides/graphql/getting_started/simple_discovery.md b/docs/content/guides/graphql/getting_started/simple_discovery.md index 5e15f870c8b..d8a44ab193e 100644 --- a/docs/content/guides/graphql/getting_started/simple_discovery.md +++ b/docs/content/guides/graphql/getting_started/simple_discovery.md @@ -92,7 +92,7 @@ Explore basic GraphQL service discovery with the Pet Store sample application. 5. Create a virtual service that defines a `Route` with a `graphqlApiRef` as the destination. In this example, all traffic to `/graphql` is handled by the GraphQL server in the Envoy proxy. {{< highlight yaml "hl_lines=12-16" >}} -cat << EOF | kubectl apply -f - +kubectl apply -f - << EOF apiVersion: gateway.solo.io/v1 kind: VirtualService metadata: diff --git a/docs/content/guides/graphql/resolver_config.md b/docs/content/guides/graphql/resolver_config.md index e6b0b7bfa45..ea2f07354a2 100644 --- a/docs/content/guides/graphql/resolver_config.md +++ b/docs/content/guides/graphql/resolver_config.md @@ -219,7 +219,7 @@ After you automatically or manually create your GraphQL resolver and schema, cre In this example, all traffic to `/graphql` is handled by the GraphQL server, which uses the `default-petstore-8080` GraphQL API. {{< highlight yaml "hl_lines=12-16" >}} -cat << EOF | kubectl apply -f - +kubectl apply -f - << EOF apiVersion: gateway.solo.io/v1 kind: VirtualService metadata: @@ -240,4 +240,4 @@ EOF ## Reference -For more information, see the [Gloo Gateway API reference for GraphQL]({{% versioned_link_path fromRoot="/reference/api/github.com/solo-io/gloo/projects/gloo/api/v1/enterprise/options/graphql/v1beta1/graphql.proto.sk/" %}}). \ No newline at end of file +For more information, see the [Gloo Gateway API reference for GraphQL]({{% versioned_link_path fromRoot="/reference/api/github.com/solo-io/gloo/projects/gloo/api/v1/enterprise/options/graphql/v1beta1/graphql.proto.sk/" %}}). diff --git a/docs/content/guides/integrations/cert_manager/_index.md b/docs/content/guides/integrations/cert_manager/_index.md index b88da056faf..1b657c83df6 100644 --- a/docs/content/guides/integrations/cert_manager/_index.md +++ b/docs/content/guides/integrations/cert_manager/_index.md @@ -62,7 +62,7 @@ For development and testing environments, you can use an AWS key pair to grant c ``` 3. Create a cluster issuer for the Let's Encrypt CA with Route 53 that refers to secret. ```shell - cat << EOF | kubectl apply -f - + kubectl apply -f - << EOF apiVersion: cert-manager.io/v1 kind: ClusterIssuer metadata: @@ -211,7 +211,7 @@ Now that the AWS access is configured, you can configure the Gloo Gateway resour ``` 2. Create the certificate for the Gloo Gateway ingress traffic along your host domain, such as `test-123456789.solo.io`. ```shell - cat << EOF | kubectl apply -f - + kubectl apply -f - << EOF apiVersion: cert-manager.io/v1 kind: Certificate metadata: @@ -234,7 +234,7 @@ Now that the AWS access is configured, you can configure the Gloo Gateway resour ``` 4. Configure Gloo Gateway's default VirtualService to refer to the TLS secret and to route the pet clinic sample app to the host domain. ```shell - cat <` to the Upstream. ```shell - cat << EOF | kubectl apply -f - + kubectl apply -f - << EOF apiVersion: gateway.solo.io/v1 kind: VirtualService metadata: @@ -395,7 +395,7 @@ Now that the server can reach the cert-manager token pod, the HTTP-01 challenge ``` 3. Configure the VirtualService to use the newly created TLS secret and to route to the pet store sample app. ```shell - cat << EOF | kubectl apply -f - + kubectl apply -f - << EOF apiVersion: gateway.solo.io/v1 kind: VirtualService metadata: diff --git a/docs/content/guides/integrations/ingress/_index.md b/docs/content/guides/integrations/ingress/_index.md index 3bfb7862a88..4a3e6813e93 100644 --- a/docs/content/guides/integrations/ingress/_index.md +++ b/docs/content/guides/integrations/ingress/_index.md @@ -52,7 +52,7 @@ great way to get a cluster up quickly. 3. Let's create a Kubernetes Ingress object to route requests to the petstore: ```yaml - cat <}} -cat <}} ```shell -cat <}}">here, then you should have exposed custom ports 31500 (for http) and 32500 (https) from your cluster's Docker container to its host machine. The purpose of this is to make it easier to access your service endpoints from your host workstation. Use the following custom installation for Gloo Gateway to publish those same ports from the proxy as well. ```bash -cat <}}">here, then you should have exposed custom ports 31500 (for http) and 32500 (https) from your cluster's Docker container to its host machine. The purpose of this is to make it easier to access your service endpoints from your host workstation. Use the following custom installation for Gloo Gateway to publish those same ports from the proxy as well. ```bash -cat <