Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 133 for syntax (0.16 sec)

  1. istioctl/pkg/dashboard/dashboard.go

    	cmd := &cobra.Command{
    		Use:   "prometheus",
    		Short: "Open Prometheus web UI",
    		Long:  `Open Istio's Prometheus dashboard`,
    		Example: `  istioctl dashboard prometheus
    
      # with short syntax
      istioctl dash prometheus
      istioctl d prometheus`,
    		RunE: func(cmd *cobra.Command, args []string) error {
    			client, err := ctx.CLIClientWithRevision(opts.Revision)
    			if err != nil {
    Go
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Apr 15 01:29:35 GMT 2024
    - 20.5K bytes
    - Viewed (0)
  2. operator/README.md

    ```bash
    istioctl manifest generate -f manifests/profiles/minimal.yaml
    ```
    
    After running the command, the Helm charts are rendered using `manifests/profiles/minimal.yaml`.
    
    ##### --set syntax
    
    The CLI `--set` option can be used to override settings within the profile.
    
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Sun Sep 17 08:27:52 GMT 2023
    - 17.5K bytes
    - Viewed (0)
  3. licenses/cloud.google.com/go/trace/LICENSE

          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue Nov 01 23:31:22 GMT 2022
    - 11.1K bytes
    - Viewed (0)
  4. licenses/github.com/AdaLogics/go-fuzz-headers/LICENSE

          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Jun 28 18:00:28 GMT 2021
    - 11.1K bytes
    - Viewed (0)
  5. licenses/cloud.google.com/go/longrunning/LICENSE

          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue Nov 01 23:31:22 GMT 2022
    - 11.1K bytes
    - Viewed (0)
  6. licenses/cloud.google.com/go/auth/LICENSE

          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue Apr 30 13:56:46 GMT 2024
    - 11.1K bytes
    - Viewed (0)
  7. licenses/github.com/google/btree/LICENSE

          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Sat Oct 26 02:47:39 GMT 2019
    - 11.1K bytes
    - Viewed (0)
  8. licenses/github.com/google/gnostic-models/LICENSE

          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Jul 24 18:16:35 GMT 2023
    - 11.1K bytes
    - Viewed (0)
  9. licenses/github.com/google/go-containerregistry/LICENSE

          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Fri Jul 30 04:02:55 GMT 2021
    - 11.1K bytes
    - Viewed (0)
  10. licenses/github.com/containerd/stargz-snapshotter/estargz/LICENSE

          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Fri Jul 30 04:02:55 GMT 2021
    - 11.1K bytes
    - Viewed (0)
Back to top