Fixed the doc links

Signed-off-by: Prafulla Mahindrakar <prafulla.mahindrakar@gmail.com>

cmd/sandbox/start.go

@@ -27,6 +27,7 @@ Mount your flytesnacks repository code inside sandbox
 ::
 
  bin/flytectl sandbox start --sourcesPath=$HOME/flyteorg/flytesnacks 
+
 Usage
 	`
 )

docs/source/conf.py

@@ -43,6 +43,7 @@
     "sphinx_copybutton",
     "sphinx_search.extension",
     "sphinx_fontawesome",
+    "sphinx_tabs.tabs",
 ]
 
 # build the templated autosummary files

docs/source/gen/flytectl_register_examples.rst

@@ -34,6 +34,7 @@ Options
   -h, --help                          help for examples
   -k, --k8ServiceAccount string        custom kubernetes service account auth role to register launch plans with.
   -l, --outputLocationPrefix string    custom output location prefix for offloaded types (files/schemas).
+      --sourceUploadPath string        Location for source code in storage.
   -v, --version string                version of the entity to be registered with flyte. (default "v1")
 
 Options inherited from parent commands

docs/source/gen/flytectl_register_files.rst

@@ -15,7 +15,18 @@ If there are already registered entities with v1 version then the command will f
 ::
 
  bin/flytectl register file  _pb_output/* -d development  -p flytesnacks
+	
+There is no difference between registration and fast registration, In fast registration, the input provided by the user is fast serialized proto that is generated by pyflyte. If Flytectl finds any source code in users's input then it will consider registration as fast registration. Flytectl finds input file by searching an archive file whose name starts with fast and has .tar.gz extension When the user runs pyflyte with --fast flag then pyflyte creates serialize proto and it also archive create source code archive file in the same directory. 
+SourceUploadPath is an optional flag. By default, flytectl will create SourceUploadPath from your storage config. In case of s3 flytectl will upload code base in s3://{{DEFINE_BUCKET_IN_STORAGE_CONFIG}}/fast/{{VERSION}}-fast{{MD5_CREATED_BY_PYFLYTE}.tar.gz}. 
+::
+
+ bin/flytectl register file  _pb_output/* -d development  -p flytesnacks  -v v2 
+	
+In case of fast registration, If the SourceUploadPath flag is defined then In this case flytectl will not use the default directory for uploading the source code, it will override the destination path on the registration  
+::
 
+ bin/flytectl register file  _pb_output/* -d development  -p flytesnacks  -v v2 --SourceUploadPath="s3://dummy/fast" 
+	
 Using archive file.Currently supported are .tgz and .tar extension files and can be local or remote file served through http/https.
 Use --archive flag.
 
@@ -29,8 +40,7 @@ Using  local tgz file.
 
  bin/flytectl register files  _pb_output.tgz -d development  -p flytesnacks --archive
 
-If you want to continue executing registration on other files ignoring the errors including version conflicts then pass in
-the continueOnError flag.
+If you want to continue executing registration on other files ignoring the errors including version conflicts then pass in the continueOnError flag.
 
 ::
 
@@ -69,7 +79,7 @@ Override Output location prefix during registration.
 ::
 
  bin/flytectl register file  _pb_output/* -d development  -p flytesnacks --continueOnError -v v2 -l "s3://dummy/prefix"
-
+	
 Usage
 
 
@@ -88,6 +98,7 @@ Options
   -h, --help                          help for files
   -k, --k8ServiceAccount string        custom kubernetes service account auth role to register launch plans with.
   -l, --outputLocationPrefix string    custom output location prefix for offloaded types (files/schemas).
+      --sourceUploadPath string        Location for source code in storage.
   -v, --version string                version of the entity to be registered with flyte. (default "v1")
 
 Options inherited from parent commands

docs/source/gen/flytectl_sandbox.rst

@@ -43,6 +43,7 @@ SEE ALSO
 ~~~~~~~~
 
 * :doc:`flytectl` 	 - flyetcl CLI tool
+* :doc:`flytectl_sandbox_exec` 	 - Execute any command in sandbox
 * :doc:`flytectl_sandbox_start` 	 - Start the flyte sandbox
 * :doc:`flytectl_sandbox_status` 	 - Get the status of the sandbox environment.
 * :doc:`flytectl_sandbox_teardown` 	 - Teardown will cleanup the sandbox environment

docs/source/gen/flytectl_sandbox_exec.rst

@@ -0,0 +1,46 @@
+.. _flytectl_sandbox_exec:
+
+flytectl sandbox exec
+---------------------
+
+Execute any command in sandbox
+
+Synopsis
+~~~~~~~~
+
+
+
+Execute command will Will run non-interactive commands and return immediately with the output.
+
+::
+ bin/flytectl sandbox exec -- ls -al 
+
+Usage
+
+::
+
+  flytectl sandbox exec [flags]
+
+Options
+~~~~~~~
+
+::
+
+  -h, --help            help for exec
+      --source string    Path of your source code
+
+Options inherited from parent commands
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+::
+
+  -c, --config string    config file (default is $HOME/.flyte/config.yaml)
+  -d, --domain string    Specifies the Flyte project's domain.
+  -o, --output string    Specifies the output type - supported formats [TABLE JSON YAML DOT DOTURL]. NOTE: dot, doturl are only supported for Workflow (default "TABLE")
+  -p, --project string   Specifies the Flyte project.
+
+SEE ALSO
+~~~~~~~~
+
+* :doc:`flytectl_sandbox` 	 - Used for testing flyte sandbox.
+

docs/source/gen/flytectl_sandbox_start.rst

@@ -19,6 +19,7 @@ Mount your flytesnacks repository code inside sandbox
 ::
 
  bin/flytectl sandbox start --sourcesPath=$HOME/flyteorg/flytesnacks 
+
 Usage
 
 
@@ -31,8 +32,8 @@ Options
 
 ::
 
-      --flytesnacks string    Path of your flytesnacks repository
-  -h, --help                 help for start
+  -h, --help            help for start
+      --source string    Path of your source code
 
 Options inherited from parent commands
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

docs/source/index.rst

@@ -10,19 +10,32 @@ Install
 Flytectl is a Golang binary and can be installed on any platform supported by
 golang
 
-Install flytectl with homebrew tap
 
-.. prompt:: bash
+.. tabs::
 
-   brew install flyteorg/homebrew-tap/flytectl
-   # Upgrade flytectl
-   brew upgrade flytectl
+  .. tab:: OSX
 
-Install flytectl with shell script
+    .. prompt:: bash $
 
-.. prompt:: bash
+       brew install flyteorg/homebrew-tap/flytectl
 
-   curl -s https://raw.githubusercontent.com/lyft/flytectl/master/install.sh | bash
+    *Upgrade* existing installation using the following command:
+
+    .. prompt:: bash $
+
+       brew upgrade flytectl
+
+  .. tab:: Other Operating systems
+
+    .. prompt:: bash $
+
+        curl -s https://raw.githubusercontent.com/lyft/flytectl/master/install.sh | bash
+
+**Test** if Flytectl is installed correctly (your Flytectl version should be > 0.2.0) using the following command:
+
+.. prompt:: bash $
+
+  flytectl version
 
 Configure
 =========
@@ -32,25 +45,73 @@ on command-line. The following configuration is useful to setup.
 Basic Configuration
 --------------------
 
-.. code-block:: yaml
-
-  admin:
-    # For GRPC endpoints you might want to use dns:///flyte.myexample.com
-    endpoint: dns:///flyte.lyft.net
-    authType: Pkce
-  logger:
-    # Logger settings to control logger output. Useful to debug logger:
-    show-source: true
-    level: 1
-
-
-Place this in $HOME/.flyte directory with name config.yaml.
-This file is searched in
-
-- $HOME/.flyte
-- currDir from where you run flytectl
-- /etc/flyte/config
-- You can pass it commandline using --config <config-file-path>
+.. tabs:: Flytectl configuration
+
+   .. tab:: Local Flyte Sandbox
+
+       Automatically configured for you by ``flytectl sandbox`` command.
+
+       .. code-block:: yaml
+
+           admin:
+             # For GRPC endpoints you might want to use dns:///flyte.myexample.com
+             endpoint: dns:///localhost:30081
+             insecure: true
+             authType: Pkce # if using authentication or just drop this. If insecure set insecure: True
+           storage:
+             connection:
+               access-key: minio
+               auth-type: accesskey
+               disable-ssl: true
+               endpoint: http://localhost:30084
+               region: my-region-here
+               secret-key: miniostorage
+             container: my-s3-bucket
+             type: minio
+
+   .. tab:: AWS Configuration
+
+       .. code-block:: yaml
+
+           admin:
+             # For GRPC endpoints you might want to use dns:///flyte.myexample.com
+             endpoint: dns:///<replace-me>
+             authType: Pkce # if using authentication or just drop this. If insecure set insecure: True
+           storage:
+             kind: s3
+             config:
+               auth_type: iam
+               region: <replace> # Example: us-east-2
+             container: <replace> # Example my-bucket. Flyte k8s cluster / service account for execution should have read access to this bucket
+
+   .. tab:: GCS Configuration
+
+       .. code-block:: yaml
+
+           admin:
+             # For GRPC endpoints you might want to use dns:///flyte.myexample.com
+             endpoint: dns:///<replace-me>
+             authType: Pkce # if using authentication or just drop this. If insecure set insecure: True
+           storage:
+             kind: google
+             config:
+               json: ""
+               project_id: <replace-me> # TODO: replace <project-id> with the GCP project ID
+               scopes: https://www.googleapis.com/auth/devstorage.read_write
+             container: <replace> # Example my-bucket. Flyte k8s cluster / service account for execution should have access to this bucket
+
+   .. tab:: Others
+
+           For other supported storage backends like Oracle, Azure, etc., refer to the configuration structure `here <https://pkg.go.dev/github.com/flyteorg/flytestdlib/storage#Config>`__.
+
+
+    Place this in $HOME/.flyte directory with name config.yaml.
+    This file is searched in
+
+    * $HOME/.flyte
+    * currDir from where you run flytectl
+    * /etc/flyte/config
+        You can pass it commandline using --config <config-file-path> aswell
 
 
 .. toctree::

docs/source/nouns.rst

@@ -28,12 +28,16 @@ Flytectl noun specify the resource on which the action needs to be performed eg:
     gen/flytectl_update_execution-queue-attribute
     gen/flytectl_update_plugin-override
     gen/flytectl_register_files
+    gen/flytectl_register_examples
     gen/flytectl_delete_execution
     gen/flytectl_delete_task-resource-attribute
     gen/flytectl_delete_cluster-resource-attribute
     gen/flytectl_delete_execution-cluster-label
     gen/flytectl_delete_execution-queue-attribute
     gen/flytectl_delete_plugin-override
-    gen/flytectl_version
     gen/flytectl_config_validate
     gen/flytectl_config_discover
+    gen/flytectl_sandbox_start
+    gen/flytectl_sandbox_status
+    gen/flytectl_sandbox_teardown
+    gen/flytectl_sandbox_exec

docs/source/verbs.rst

@@ -7,8 +7,11 @@ Flytectl verbs specify the actions to be performed on the resources like create/
     :caption: Verbs
 
     gen/flytectl_create
+    gen/flytectl_completion
     gen/flytectl_get
     gen/flytectl_update
     gen/flytectl_delete
     gen/flytectl_register
     gen/flytectl_config
+    gen/flytectl_sandbox
+    gen/flytectl_version