Skip to main content

resoto-plugin-cleanup-untagged

Cleanup Untagged Plugin for Resoto

This plugin deletes cloud resources that are missing mandatory tags after a certain amount of time has passed since their creation.

Usage

In resh execute

> config edit resoto.worker

and find the following section

plugin_cleanup_untagged:
  # Configuration for the plugin
  config:
    default:
      age: '2h'
    tags:
      - 'owner'
      - 'expiration'
    kinds:
      - 'aws_ec2_instance'
      - 'aws_ec2_volume'
      - 'aws_vpc'
      - 'aws_cloudformation_stack'
      - 'aws_elb'
      - 'aws_alb'
      - 'aws_alb_target_group'
      - 'aws_eks_cluster'
      - 'aws_eks_nodegroup'
      - 'example_instance'
      - 'example_network'
    accounts:
      aws:
        068564737731:
          name: 'playground'
          age: '7d'
        '575584959047':
          name: 'eng-sre'
      example:
        Example Account:
          name: 'Example Account'
  # Enable plugin?
  enabled: false

Config section format

The config section consists of four sub-sections. default, tags, classes and accounts. The default section specifies the default age a resource must have before we enforce mandatory tags on it. For instance if age is set to 2h this means that whatever mechanism creates a resource has two hours to add those mandatory tags.

The tags section is a list of tag names that MUST exist on every resource class specified in classes. The classes section is a list of resource class names for which tags specified in the tags list must exist.

The accounts section contains a dictionary with cloud IDs as keys (e.g. aws) and account IDs for which tags will be enforced as values (e.g. 068564737731). Those in turn contain a name and optionally an age override.

The following age units are valid:

weeks
days
hours
minutes

Each of them can be abbreviated down to one letter. E.g. 7d, 24h, 60m, etc. A space in between the numeric and the unit is optional, meaning 7d and 7 days are equivalent.

Metadata

Release files for resoto-plugin-cleanup-untagged 3.7.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for resoto-plugin-cleanup-untagged 3.7.0
File Size Uploaded Provenance Actions
resoto-plugin-cleanup-untagged-3.7.0.tar.gz 4.8 kB Without provenance Details for resoto-plugin-cleanup-untagged-3.7.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for resoto-plugin-cleanup-untagged 3.7.0
File Interpreter ABI Platform Actions
resoto_plugin_cleanup_untagged-3.7.0-py3-none-any.whl Python 3 none any Details for resoto_plugin_cleanup_untagged-3.7.0-py3-none-any.whl

Total release size: 9.8 kB

Release files / resoto-plugin-cleanup-untagged-3.7.0.tar.gz

Download URL resoto-plugin-cleanup-untagged-3.7.0.tar.gz
Size 4.8 kB
Tags Source
SHA-256 checksum
How to use checksums
fa425aa11ff567c0eebf6b129416ba949be921dbbc2f5b8568d5bd12e0a6bb37
BLAKE2b-256 checksum
How to use checksums
c0b451c7eec8362e49f7dd544f48a32f30a2f2b2ff2227c41b75d5f76f118c7f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.2 CPython/3.11.5

Release files / resoto_plugin_cleanup_untagged-3.7.0-py3-none-any.whl

Download URL resoto_plugin_cleanup_untagged-3.7.0-py3-none-any.whl
Size 5.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6459259955d673112e801a1149decead87e1b829815e157be91857578dcceb1b
BLAKE2b-256 checksum
How to use checksums
da7c924d49808ca162e22fa81e6fe94d5b1288eb022f96efd182879f5d700eef
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.2 CPython/3.11.5

Security for resoto-plugin-cleanup-untagged 3.7.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

3.7.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page