Skip to content

encrypt_secrets no longer available #1083

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 17, 2021
Merged

encrypt_secrets no longer available #1083

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 1 addition & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -233,7 +233,7 @@ You are now ready to run action workloads on self hosted runner. Remember that b

### Encryption

The module support 3 scenario's to manage environment secrets and private key of the Lambda functions.
The module support 2 scenarios to manage environment secrets and private key of the Lambda functions.

#### Encrypted via a module managed KMS key (default) <!-- omit in toc -->

Expand All @@ -257,10 +257,6 @@ module "runners" {

```

#### No encryption <!-- omit in toc -->

Not advised but you can disable the encryption as by setting the variable `encrypt_secrets` to `false`.

### Idle runners

The module will scale down to zero runners be default, by specifying a `idle_config` config idle runners can be kept active. The scale down lambda checks if any of the cron expressions matches the current time with a marge of 5 seconds. When there is a match the number of runners specified in the idle config will be kept active. In case multiple cron expressions matches only the first one is taken in to account. Below an idle configuration for keeping runners active from 9 to 5 on working days.
Expand Down