Run Ecspresso

Version updated for cloudposse/github-action-run-ecspresso to version 0.2.0.

  • This publisher is shown as ‘verified’ by GitHub.
  • This action is used across all versions by 3 repositories.

Go to the GitHub Marketplace to find the latest changes.

Release notes

what

  • Application repositories can now run DB Migrations and other Ecspresso tasks while only having a partial task definition in their repository. e.g.
{
  "containerDefinitions": [
    {
      "name": "app",
      "image": "{{ must_env `IMAGE` }}"
    }
  ],
  "cpu": "256",
  "memory": "1024"
}

The rest can be fetched from S3, which will be merged. This S3 Task Template is populated by our ECS Service component with the variable s3_mirror_name which enables these modules

This action will then merge the task definition before running ecspresso commands.

why

  • We want the infrastructure repo to control the infrastructure things of the application deployment process, such as volumes (getting the ID is better through terraform than hardcoding). But we want the application (GitHub Repo) to decide the image, CPU, env or any other application related change.

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

Detected Package Files

  • .github/workflows/auto-readme.yml (github-actions)
  • .github/workflows/feature-branch.yml (github-actions)
  • .github/workflows/main-branch.yaml (github-actions)
  • .github/workflows/test-negative.yml (github-actions)
  • .github/workflows/test-positive.yml (github-actions)
  • .github/workflows/test-validate-failed.yml (github-actions)
  • action.yml (github-actions)

Configuration Summary

Based on the default config’s presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the “What to Expect” section below will be updated the next time Renovate runs.

What to Expect

With your current configuration, Renovate will create 4 Pull Requests:

  • Schedule: [“at any time”]
  • Branch name: renovate/cloudposse-actions-0.x
  • Merge into: main
  • Upgrade cloudposse/actions to 0.33.0
  • Schedule: [“at any time”]
  • Branch name: renovate/joellefkowitz-random-env-1.x
  • Merge into: main
  • Upgrade joellefkowitz/random-env to v1.2.0
  • Schedule: [“at any time”]
  • Branch name: renovate/actions-checkout-3.x
  • Merge into: main
  • Upgrade actions/checkout to v3

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn’t swamp any CI resources or overwhelm the project. See docs for prhourlylimit for details.

❓ Got questions? Check out Renovate’s Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.

This PR has been generated by Mend Renovate. View repository job log here.