Skip to content

Change resource tagging scheme #88

@hrodmn

Description

@hrodmn

Right now we are using AWS resource tags in an aggressive way that is triggering a lot of unnecessary re-deployments. We set tags based on the git commit, the author (individual who runs the deployment), and a version that is calculated by npm.js. We should remove those volatile tags and use GitHub actions to track the provenance of each deployment.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions