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: doc/overview.rst
+50-46
Original file line number
Diff line number
Diff line change
@@ -183,77 +183,57 @@ Here is an example:
183
183
# When you are done using your endpoint
184
184
algo.delete_endpoint()
185
185
186
-
Git Support
187
-
-----------
188
-
If you have your training scripts or in your GitHub (or other Git) repository, you can use them directly without the
189
-
trouble to download them locally. Git support can be enabled simply by providing ``git_config`` parameter
186
+
Use Scripts Stored in a Git Repository
187
+
--------------------------------------
188
+
When you create an estimator, you can specify a training script that is stored in a GitHub or other Git repository as the entry point for the estimator, so that you don't have to download the scripts locally.
189
+
If you fo so, source directory and dependencies should be in the same repo if they are needed. Git support can be enabled simply by providing ``git_config`` parameter
190
190
when creating an ``Estimator`` object. If Git support is enabled, then ``entry_point``, ``source_dir`` and ``dependencies``
191
-
should all be relative paths in the Git repo if provided. Note that if you decided to use Git support, then all your
192
-
training scripts should be in a single Git repo.
191
+
should be relative paths in the Git repo if provided.
193
192
194
-
The ``git_config`` parameter includes arguments ``repo``, ``branch``, ``commit``, ``2FA_enabled``, ``username``,
195
-
``password`` and ``token``. Except for ``repo``, the other arguments are optional. ``repo`` specifies the Git repository
193
+
The ``git_config`` parameter includes fields ``repo``, ``branch``, ``commit``, ``2FA_enabled``, ``username``,
194
+
``password`` and ``token``. The ``repo`` field is required. All other fields are optional. ``repo`` specifies the Git repository
196
195
that you want to use. If ``branch`` is not provided, master branch will be used. If ``commit`` is not provided,
197
196
the latest commit in the required branch will be used.
198
197
199
-
``2FA_enabled``, ``username``, ``password`` and ``token`` are for authentication purpose. ``2FA_enabled`` should
200
-
be 'True' or 'False', providing the information whether two-factor authentication is enabled for the GitHub (or other Git) account.
201
-
If ``2FA_enabled`` is not provided, we consider 2FA as disabled.
198
+
``2FA_enabled``, ``username``, ``password`` and ``token`` are used for authentication. Set ``2FA_enabled`` to 'True' if
199
+
two-factor authentication is enabled for the GitHub (or other Git) account, otherwise set it to 'False'.
200
+
If you do not provide a value for ``2FA_enabled``, a default value of 'False' is used.
202
201
203
-
If ``repo`` is an ssh url, you should either have no passphrase for the ssh key pairs, or have the ssh-agent configured
204
-
so that you will not be prompted for ssh passphrase when you do 'git clone' command with ssh urls. For ssh urls, it
205
-
makes no difference whether the 2FA is enabled or disabled.
202
+
If ``repo`` is an SSH URL, you should either have no passphrase for the SSH key pairs, or have the ``ssh-agent`` configured
203
+
so that you are not prompted for the SSH passphrase when you run a ``git clone`` command with SSH URLs. For SSH URLs, it
204
+
does not matter whether two-factor authentication is enabled.
206
205
207
-
If ``repo`` is an https url, 2FA matters. When 2FA is disabled, either ``token`` or ``username``+``password`` will be
206
+
If ``repo`` is an https URL, 2FA matters. When 2FA is disabled, either ``token`` or ``username``+``password`` will be
208
207
used for authentication if provided (``token`` prioritized). When 2FA is enabled, only token will be used for
209
208
authentication if provided. If required authentication info is not provided, python SDK will try to use local
210
209
credentials storage to authenticate. If that fails either, an error message will be thrown.
211
210
212
-
Here are some ways to specify ``git_config``:
211
+
Here are some examples of creating estimators with Git support:
213
212
214
213
.. code:: python
215
214
216
-
# The following three examples do not provide Git credentials, so python SDK will try to use
217
-
# local credential storage.
218
-
219
-
# Specifies the git_config parameter
215
+
# Specifies the git_config parameter. This example does not provide Git credentials, so python SDK will try
0 commit comments