From 925b0a9baf5d90a1986f3e55eb26b2f9ea4f2394 Mon Sep 17 00:00:00 2001 From: Future Outlier Date: Thu, 12 Oct 2023 21:29:54 +0800 Subject: [PATCH] make bash command the same format Signed-off-by: Future Outlier --- rsts/deployment/agents/databricks.rst | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/rsts/deployment/agents/databricks.rst b/rsts/deployment/agents/databricks.rst index 9d03ad65c0..fa17b37810 100644 --- a/rsts/deployment/agents/databricks.rst +++ b/rsts/deployment/agents/databricks.rst @@ -268,16 +268,17 @@ You have to set the Databricks token to the Flyte configuration. 1. Install flyteagent pod using helm - .. code-block:: bash + .. code-block:: cd flyte/charts/flyteagent + + .. code-block:: helm install flyteagent . -n flyte - 2. Get the base64 value of your Databricks token. - .. code-block:: bash + .. code-block:: echo -n "" | base64 @@ -320,13 +321,13 @@ Upgrade the deployment .. group-tab:: Demo cluster - .. code-block:: bash + .. code-block:: kubectl rollout restart deployment flyte-sandbox -n flyte .. group-tab:: Helm chart - .. code-block:: bash + .. code-block:: helm upgrade flyteorg/flyte-binary -n --values @@ -353,4 +354,4 @@ Wait for the upgrade to complete. You can check the status of the deployment pod Make sure you enable `custom containers `__ - on your Databricks cluster before you trigger the workflow. \ No newline at end of file + on your Databricks cluster before you trigger the workflow.