snapctl 0.38.1__tar.gz → 0.38.3__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Potentially problematic release.
This version of snapctl might be problematic. Click here for more details.
- {snapctl-0.38.1 → snapctl-0.38.3}/PKG-INFO +14 -12
- {snapctl-0.38.1 → snapctl-0.38.3}/README.md +13 -11
- {snapctl-0.38.1 → snapctl-0.38.3}/pyproject.toml +1 -1
- {snapctl-0.38.1 → snapctl-0.38.3}/snapctl/config/constants.py +1 -1
- {snapctl-0.38.1 → snapctl-0.38.3}/LICENSE +0 -0
- {snapctl-0.38.1 → snapctl-0.38.3}/snapctl/__init__.py +0 -0
- {snapctl-0.38.1 → snapctl-0.38.3}/snapctl/__main__.py +0 -0
- {snapctl-0.38.1 → snapctl-0.38.3}/snapctl/commands/__init__.py +0 -0
- {snapctl-0.38.1 → snapctl-0.38.3}/snapctl/commands/byogs.py +0 -0
- {snapctl-0.38.1 → snapctl-0.38.3}/snapctl/commands/byosnap.py +0 -0
- {snapctl-0.38.1 → snapctl-0.38.3}/snapctl/commands/game.py +0 -0
- {snapctl-0.38.1 → snapctl-0.38.3}/snapctl/commands/generate.py +0 -0
- {snapctl-0.38.1 → snapctl-0.38.3}/snapctl/commands/snapend.py +0 -0
- {snapctl-0.38.1 → snapctl-0.38.3}/snapctl/config/__init__.py +0 -0
- {snapctl-0.38.1 → snapctl-0.38.3}/snapctl/config/endpoints.py +0 -0
- {snapctl-0.38.1 → snapctl-0.38.3}/snapctl/config/hashes.py +0 -0
- {snapctl-0.38.1 → snapctl-0.38.3}/snapctl/main.py +0 -0
- {snapctl-0.38.1 → snapctl-0.38.3}/snapctl/types/__init__.py +0 -0
- {snapctl-0.38.1 → snapctl-0.38.3}/snapctl/types/definitions.py +0 -0
- {snapctl-0.38.1 → snapctl-0.38.3}/snapctl/utils/__init__.py +0 -0
- {snapctl-0.38.1 → snapctl-0.38.3}/snapctl/utils/echo.py +0 -0
- {snapctl-0.38.1 → snapctl-0.38.3}/snapctl/utils/helper.py +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.1
|
|
2
2
|
Name: snapctl
|
|
3
|
-
Version: 0.38.
|
|
3
|
+
Version: 0.38.3
|
|
4
4
|
Summary: Snapser CLI Tool
|
|
5
5
|
Author: Ajinkya Apte
|
|
6
6
|
Author-email: aj@snapser.com
|
|
@@ -17,7 +17,10 @@ Requires-Dist: requests (>=2.28.2,<3.0.0)
|
|
|
17
17
|
Requires-Dist: typer[all] (>=0.12.3,<0.13.0)
|
|
18
18
|
Description-Content-Type: text/markdown
|
|
19
19
|
|
|
20
|
-
# Snapser CLI
|
|
20
|
+
# Snapser CLI
|
|
21
|
+
|
|
22
|
+
Snapser has developed a CLI tool called **snapctl** that can be used on MaxOSX, Linux and Windows machines.
|
|
23
|
+
Snapctl will be the best way for game studios to integrate Snapser into their build pipelines.
|
|
21
24
|
|
|
22
25
|
## Dependencies
|
|
23
26
|
|
|
@@ -53,12 +56,10 @@ If you also have Python 2.X on your machine, you may have to run the following c
|
|
|
53
56
|
pip3 install --user snapctl
|
|
54
57
|
```
|
|
55
58
|
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
**C:\Users\username\AppData\Roaming\Python\Python39\Scripts**.
|
|
61
|
-
</Note>
|
|
59
|
+
**IMPORTANT**: After you install snapctl you may have to add the python bin folder to your
|
|
60
|
+
path. For example, on MacOSX this is usually **~/Library/Python/3.9/bin**. On
|
|
61
|
+
Windows this is usually
|
|
62
|
+
**C:\Users\username\AppData\Roaming\Python\Python39\Scripts**.
|
|
62
63
|
|
|
63
64
|
## Upgrade
|
|
64
65
|
|
|
@@ -77,10 +78,8 @@ In the left navigation click on **Developer** which will bring up your Personal
|
|
|
77
78
|
If you have not generated an API Key yet click on the **Generate** button to generate a new key.
|
|
78
79
|
You can generate up to 3 API Keys per user account.
|
|
79
80
|
|
|
80
|
-
|
|
81
|
-
|
|
82
|
-
to see it again.
|
|
83
|
-
</Note>
|
|
81
|
+
**IMPORTANT**: Please make sure you save your API key in a safe place. You will not be able
|
|
82
|
+
to see it again.
|
|
84
83
|
|
|
85
84
|
### Setup a local config
|
|
86
85
|
|
|
@@ -288,6 +287,9 @@ snapctl byosnap publish-image $byosnap_sid --tag $image_tag --skip-build
|
|
|
288
287
|
Publish a new version for your Snap. Only after your Snap version is published, you will be able
|
|
289
288
|
to use your snap in your Snapend. This command should be run after `push` or `publish-image` commands.
|
|
290
289
|
|
|
290
|
+
IMPORTANT: You need to have $byosnapProfile to run this command. BYOSnap profile is a JSON configuration
|
|
291
|
+
of your BYOSnap for the development, staging and production environments.
|
|
292
|
+
|
|
291
293
|
```
|
|
292
294
|
# Help for the byosnap command
|
|
293
295
|
snapctl byosnap publish-version --help
|
|
@@ -1,4 +1,7 @@
|
|
|
1
|
-
# Snapser CLI
|
|
1
|
+
# Snapser CLI
|
|
2
|
+
|
|
3
|
+
Snapser has developed a CLI tool called **snapctl** that can be used on MaxOSX, Linux and Windows machines.
|
|
4
|
+
Snapctl will be the best way for game studios to integrate Snapser into their build pipelines.
|
|
2
5
|
|
|
3
6
|
## Dependencies
|
|
4
7
|
|
|
@@ -34,12 +37,10 @@ If you also have Python 2.X on your machine, you may have to run the following c
|
|
|
34
37
|
pip3 install --user snapctl
|
|
35
38
|
```
|
|
36
39
|
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
**C:\Users\username\AppData\Roaming\Python\Python39\Scripts**.
|
|
42
|
-
</Note>
|
|
40
|
+
**IMPORTANT**: After you install snapctl you may have to add the python bin folder to your
|
|
41
|
+
path. For example, on MacOSX this is usually **~/Library/Python/3.9/bin**. On
|
|
42
|
+
Windows this is usually
|
|
43
|
+
**C:\Users\username\AppData\Roaming\Python\Python39\Scripts**.
|
|
43
44
|
|
|
44
45
|
## Upgrade
|
|
45
46
|
|
|
@@ -58,10 +59,8 @@ In the left navigation click on **Developer** which will bring up your Personal
|
|
|
58
59
|
If you have not generated an API Key yet click on the **Generate** button to generate a new key.
|
|
59
60
|
You can generate up to 3 API Keys per user account.
|
|
60
61
|
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
to see it again.
|
|
64
|
-
</Note>
|
|
62
|
+
**IMPORTANT**: Please make sure you save your API key in a safe place. You will not be able
|
|
63
|
+
to see it again.
|
|
65
64
|
|
|
66
65
|
### Setup a local config
|
|
67
66
|
|
|
@@ -269,6 +268,9 @@ snapctl byosnap publish-image $byosnap_sid --tag $image_tag --skip-build
|
|
|
269
268
|
Publish a new version for your Snap. Only after your Snap version is published, you will be able
|
|
270
269
|
to use your snap in your Snapend. This command should be run after `push` or `publish-image` commands.
|
|
271
270
|
|
|
271
|
+
IMPORTANT: You need to have $byosnapProfile to run this command. BYOSnap profile is a JSON configuration
|
|
272
|
+
of your BYOSnap for the development, staging and production environments.
|
|
273
|
+
|
|
272
274
|
```
|
|
273
275
|
# Help for the byosnap command
|
|
274
276
|
snapctl byosnap publish-version --help
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|