cloudsnorkel.cdk-github-runners 0.16.0__tar.gz → 0.16.1__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.16.1}/PKG-INFO +3 -2
  2. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.16.1}/README.md +2 -1
  3. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.16.1}/setup.py +2 -2
  4. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.16.1}/src/cloudsnorkel/cdk_github_runners/__init__.py +6 -2
  5. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.16.1}/src/cloudsnorkel/cdk_github_runners/_jsii/__init__.py +2 -2
  6. cloudsnorkel_cdk_github_runners-0.16.1/src/cloudsnorkel/cdk_github_runners/_jsii/cdk-github-runners@0.16.1.jsii.tgz +0 -0
  7. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.16.1/src/cloudsnorkel.cdk_github_runners.egg-info}/PKG-INFO +3 -2
  8. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.16.1}/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.16.1}/LICENSE +0 -0
  11. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.16.1}/MANIFEST.in +0 -0
  12. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.16.1}/pyproject.toml +0 -0
  13. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.16.1}/setup.cfg +0 -0
  14. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.16.1}/src/cloudsnorkel/cdk_github_runners/py.typed +0 -0
  15. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.16.1}/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.16.1}/src/cloudsnorkel.cdk_github_runners.egg-info/requires.txt +0 -0
  17. {cloudsnorkel_cdk_github_runners-0.16.0 → cloudsnorkel_cdk_github_runners-0.16.1}/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.16.1
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>
@@ -663,7 +663,8 @@ Other useful metrics to track:
663
663
 
664
664
  ## Known Issues
665
665
 
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.
666
+ 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.
667
+ 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
668
 
668
669
  ## Getting Help
669
670
 
@@ -635,7 +635,8 @@ Other useful metrics to track:
635
635
 
636
636
  ## Known Issues
637
637
 
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.
638
+ 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.
639
+ 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
640
 
640
641
  ## Getting Help
641
642
 
@@ -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.16.1",
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.16.1.jsii.tgz"
30
30
  ],
31
31
  "cloudsnorkel.cdk_github_runners": [
32
32
  "py.typed"
@@ -636,7 +636,8 @@ Other useful metrics to track:
636
636
 
637
637
  ## Known Issues
638
638
 
639
- 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.
639
+ 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.
640
+ 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.
640
641
 
641
642
  ## Getting Help
642
643
 
@@ -1459,7 +1460,7 @@ class AwsImageBuilderRunnerImageBuilderProps:
1459
1460
  storage_size: typing.Optional["_aws_cdk_ceddda9d.Size"] = None,
1460
1461
  ) -> None:
1461
1462
  '''
1462
- :param ami_tags: (experimental) Additional tags to apply to the AMI built by this builder. These additional tags are set on top of ``Name``, ``GitHubRunners:Stack``, and ``GitHubRunners:Builder``. You may override the built-in tags. Default: no additional tags
1463
+ :param ami_tags: (experimental) Additional tags to apply to the AMI built by this builder. These additional tags are set on top of ``Name``, ``GitHubRunners:Stack``, and ``GitHubRunners:Builder``. You may override the built-in tags. Overriding ``GitHubRunners:Stack`` will stop old AMIs from being deleted, as the image cleaner is only allowed to touch AMIs tagged with the name of the stack it lives in. You will have to delete those AMIs yourself. Default: no additional tags
1463
1464
  :param fast_launch_options: (experimental) Options for fast launch. This is only supported for Windows AMIs. Default: disabled
1464
1465
  :param instance_type: (experimental) The instance type used to build the image. Default: m6i.large
1465
1466
  :param storage_size: (experimental) Size of volume available for builder instances. This modifies the boot volume size and doesn't add any additional volumes. Use this if you're building images with big components and need more space. Default: default size for AMI (usually 30GB for Linux and 50GB for Windows)
@@ -1491,6 +1492,9 @@ class AwsImageBuilderRunnerImageBuilderProps:
1491
1492
  These additional tags are set on top of ``Name``, ``GitHubRunners:Stack``, and ``GitHubRunners:Builder``.
1492
1493
  You may override the built-in tags.
1493
1494
 
1495
+ Overriding ``GitHubRunners:Stack`` will stop old AMIs from being deleted, as the image cleaner is only allowed to touch AMIs tagged with the name
1496
+ of the stack it lives in. You will have to delete those AMIs yourself.
1497
+
1494
1498
  :default: no additional tags
1495
1499
 
1496
1500
  :stability: experimental
@@ -19,9 +19,9 @@ import constructs._jsii
19
19
 
20
20
  __jsii_assembly__ = jsii.JSIIAssembly.load(
21
21
  "@cloudsnorkel/cdk-github-runners",
22
- "0.16.0",
22
+ "0.16.1",
23
23
  __name__[0:-6],
24
- "cdk-github-runners@0.16.0.jsii.tgz",
24
+ "cdk-github-runners@0.16.1.jsii.tgz",
25
25
  )
26
26
 
27
27
  __all__ = [
@@ -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.16.1
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>
@@ -663,7 +663,8 @@ Other useful metrics to track:
663
663
 
664
664
  ## Known Issues
665
665
 
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.
666
+ 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.
667
+ 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
668
 
668
669
  ## Getting Help
669
670
 
@@ -11,4 +11,4 @@ src/cloudsnorkel.cdk_github_runners.egg-info/top_level.txt
11
11
  src/cloudsnorkel/cdk_github_runners/__init__.py
12
12
  src/cloudsnorkel/cdk_github_runners/py.typed
13
13
  src/cloudsnorkel/cdk_github_runners/_jsii/__init__.py
14
- src/cloudsnorkel/cdk_github_runners/_jsii/cdk-github-runners@0.16.0.jsii.tgz
14
+ src/cloudsnorkel/cdk_github_runners/_jsii/cdk-github-runners@0.16.1.jsii.tgz