cloudsnorkel.cdk-github-runners 0.16.0__tar.gz → 0.17.0__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.
Files changed (17) hide show
  1. {cloudsnorkel_cdk_github_runners-0.16.0/src/cloudsnorkel.cdk_github_runners.egg-info → cloudsnorkel_cdk_github_runners-0.17.0}/PKG-INFO +3 -4
  2. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.17.0}/README.md +2 -3
  3. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.17.0}/setup.py +2 -2
  4. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.17.0}/src/cloudsnorkel/cdk_github_runners/__init__.py +69 -995
  5. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.17.0}/src/cloudsnorkel/cdk_github_runners/_jsii/__init__.py +2 -2
  6. cloudsnorkel_cdk_github_runners-0.17.0/src/cloudsnorkel/cdk_github_runners/_jsii/cdk-github-runners@0.17.0.jsii.tgz +0 -0
  7. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.17.0/src/cloudsnorkel.cdk_github_runners.egg-info}/PKG-INFO +3 -4
  8. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.17.0}/src/cloudsnorkel.cdk_github_runners.egg-info/SOURCES.txt +1 -1
  9. cloudsnorkel_cdk_github_runners-0.16.0/src/cloudsnorkel/cdk_github_runners/_jsii/cdk-github-runners@0.16.0.jsii.tgz +0 -0
  10. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.17.0}/LICENSE +0 -0
  11. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.17.0}/MANIFEST.in +0 -0
  12. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.17.0}/pyproject.toml +0 -0
  13. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.17.0}/setup.cfg +0 -0
  14. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.17.0}/src/cloudsnorkel/cdk_github_runners/py.typed +0 -0
  15. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.17.0}/src/cloudsnorkel.cdk_github_runners.egg-info/dependency_links.txt +0 -0
  16. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.17.0}/src/cloudsnorkel.cdk_github_runners.egg-info/requires.txt +0 -0
  17. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.17.0}/src/cloudsnorkel.cdk_github_runners.egg-info/top_level.txt +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.1
2
2
  Name: cloudsnorkel.cdk-github-runners
3
- Version: 0.16.0
3
+ Version: 0.17.0
4
4
  Summary: CDK construct to create GitHub Actions self-hosted runners. Creates ephemeral runners on demand. Easy to deploy and highly customizable.
5
5
  Home-page: https://github.com/CloudSnorkel/cdk-github-runners.git
6
6
  Author: Amir Szekely<amir@cloudsnorkel.com>
@@ -100,8 +100,6 @@ The best provider to use mostly depends on your current infrastructure. When in
100
100
  * ECS is useful when you want to control the infrastructure, like leaving the runner host running for faster startups
101
101
  * Lambda is useful for short jobs that can work within time, size and readonly system constraints
102
102
 
103
- You can also create your own provider by implementing `IRunnerProvider`.
104
-
105
103
  ## Installation
106
104
 
107
105
  1. Install and use the appropriate package
@@ -663,7 +661,8 @@ Other useful metrics to track:
663
661
 
664
662
  ## Known Issues
665
663
 
666
- 1. Docker images built with AWS Image Builder (by default only Windows Docker images) might not be fully rolled back on deployment failure. If your stack fails to deploy after an image was already built, the new image will stay around. It will be automatically replaced on the next build interval but that might take up to 7 days with default settings (`rebuildInterval`). It's recommended to not leave stacks in `UPDATE_ROLLBACK_COMPLETE` state if you're using Windows Docker images.
664
+ 1. Runner images built during a failed deployment are not rolled back. If your stack fails to deploy after an image was already built, the new image will stay in use. The image will be automatically replaced on the next build interval, but that might take up to 7 days with default settings (`rebuildInterval`). It's recommended to not leave stacks in `UPDATE_ROLLBACK_COMPLETE` state. Deploying again with the configuration you want will rebuild the images and get everything back in sync.
665
+ 2. Library downgrades are not well tested. We work hard to keep backwards compatibility, but downgrading to an older version of the library may lead to unexpected issues. For example, downgrading from 0.16.1 may result in runner images being deleted. They will be rebuilt on the next build interval, but that might take up to 7 days with default settings (`rebuildInterval`). It's recommended to not downgrade the library unless you know what you're doing.
667
666
 
668
667
  ## Getting Help
669
668
 
@@ -72,8 +72,6 @@ The best provider to use mostly depends on your current infrastructure. When in
72
72
  * ECS is useful when you want to control the infrastructure, like leaving the runner host running for faster startups
73
73
  * Lambda is useful for short jobs that can work within time, size and readonly system constraints
74
74
 
75
- You can also create your own provider by implementing `IRunnerProvider`.
76
-
77
75
  ## Installation
78
76
 
79
77
  1. Install and use the appropriate package
@@ -635,7 +633,8 @@ Other useful metrics to track:
635
633
 
636
634
  ## Known Issues
637
635
 
638
- 1. Docker images built with AWS Image Builder (by default only Windows Docker images) might not be fully rolled back on deployment failure. If your stack fails to deploy after an image was already built, the new image will stay around. It will be automatically replaced on the next build interval but that might take up to 7 days with default settings (`rebuildInterval`). It's recommended to not leave stacks in `UPDATE_ROLLBACK_COMPLETE` state if you're using Windows Docker images.
636
+ 1. Runner images built during a failed deployment are not rolled back. If your stack fails to deploy after an image was already built, the new image will stay in use. The image will be automatically replaced on the next build interval, but that might take up to 7 days with default settings (`rebuildInterval`). It's recommended to not leave stacks in `UPDATE_ROLLBACK_COMPLETE` state. Deploying again with the configuration you want will rebuild the images and get everything back in sync.
637
+ 2. Library downgrades are not well tested. We work hard to keep backwards compatibility, but downgrading to an older version of the library may lead to unexpected issues. For example, downgrading from 0.16.1 may result in runner images being deleted. They will be rebuilt on the next build interval, but that might take up to 7 days with default settings (`rebuildInterval`). It's recommended to not downgrade the library unless you know what you're doing.
639
638
 
640
639
  ## Getting Help
641
640
 
@@ -5,7 +5,7 @@ kwargs = json.loads(
5
5
  """
6
6
  {
7
7
  "name": "cloudsnorkel.cdk-github-runners",
8
- "version": "0.16.0",
8
+ "version": "0.17.0",
9
9
  "description": "CDK construct to create GitHub Actions self-hosted runners. Creates ephemeral runners on demand. Easy to deploy and highly customizable.",
10
10
  "license": "Apache-2.0",
11
11
  "url": "https://github.com/CloudSnorkel/cdk-github-runners.git",
@@ -26,7 +26,7 @@ kwargs = json.loads(
26
26
  ],
27
27
  "package_data": {
28
28
  "cloudsnorkel.cdk_github_runners._jsii": [
29
- "cdk-github-runners@0.16.0.jsii.tgz"
29
+ "cdk-github-runners@0.17.0.jsii.tgz"
30
30
  ],
31
31
  "cloudsnorkel.cdk_github_runners": [
32
32
  "py.typed"