8000 GitHub - Sage-Bionetworks/action-pipenv-aws-setup: Common github action setup steps
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Sage-Bionetworks/action-pipenv-aws-setup

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

13 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

action-pipenv-aws-setup

Common github action setup steps. This is a common infrastructure setup which:

  1. Checks out code
  2. Sets up python
  3. Sets up pipenv
  4. Installs dependencies
  5. Assumes an AWS role with OIDC integration. This requires that OIDC integration with an IAM role is setup so that the github repo can assume the role to deploy to your AWS account. See below for more information.

Recent updates

v3 update

We've recently released a v3 of this action that updates to using OIDC integration with the aws-actions/configure-aws-credentials action.

This is a breaking change.

You should update your action references to v3 once you have setup OIDC integration. See To setup github OIDC under Github OIDC Setup README for how to setup your github repo with OIDC integration for use with v3 of this repo. See the following steps + example for how to implement the integration in your github actions workflow for use with v3 of this action.

Other minor changes include making more inputs for user to specify when implementing this action into their Github (GH) Actions workflow as well as upgrading all actions' versions.

Getting Started

For v3 - present of this action

There are some inputs that the user can specify values for in this action. See action.yaml for further details for this action's inputs.

For inputs related to aws credentials and role assuming, see configure-aws-credentials-for-github-actions for the full documenation including limitations on those inputs.

Also be sure to include the following permissions in your GH Actions workflow for the job or job(s) that use this action:

# These permissions are needed to interact with GitHub's OIDC Token endpoint.
permissions:
    id-token: write
    contents: read

For v1-v2 of this action

Highly recommended to update to using OIDC integration.

Contributing

Read through the contribution guidelines for more information.

About

Common github action setup steps

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Contributors 2

  •  
  •  
0