create .env
or shell script via AWS SSM parameters path
- uses: deptno/action-aws-ssm-to-dotenv@v1.3.1
env:
AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }} # required
AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }} # required
AWS_DEFAULT_REGION: ap-northeast-2 # required
with:
ssm-path: /opensource/action-aws-ssm-to-dotenv # required
format: shell
output: .env.development
set-as-env: false
set-case: upper
prefix-paths: true
prefix: SSM_
decryption: true
action_aws_ssm_to_dotenv
will append data to output file(1.3.0)
AWS Systems Manager > Parameter Store > Path
optional, default=dotenv
- dotenv: KEY="value" (default)
- shell: export KEY="value"
- yaml: KEY: "value"
- json: {"KEY": "value"}
- plain: value
output filename
add prefix to exported variable name
eg) prefix: ACTION_
will export ACTION_ENV_VAR="value"
Sets the values as environment variables for this GitHub Actions Job
Transform the keys to upper
, lower
, or none
for unchanged
If true
the relative path from the ssm-paths value to the parameter is prefixed on the key.
So if the key full path is /envs/dev/mysql_user then if this is true and ssm-paths value was
"/env/" the key presented would be "dev_mysql_user"'
should parameters be decrypted?
MIT