Skip to content

ENSY-68-repo-setup#1

Merged
ehanson8 merged 3 commits intomainfrom
ENSY-68-repo-setup
May 18, 2022
Merged

ENSY-68-repo-setup#1
ehanson8 merged 3 commits intomainfrom
ENSY-68-repo-setup

Conversation

@ehanson8
Copy link
Contributor

@ehanson8 ehanson8 commented May 17, 2022

Helpful background context

Initial repo setup for the ppod lambda

What are the relevant tickets?

https://mitlibraries.atlassian.net/browse/ENSY-68

Developer

  • All new ENV is documented in README
  • Stakeholder approval has been confirmed (or is not needed)

Code Reviewer

  • The commit message is clear and follows our guidelines
    (not just this pull request message)
  • There are appropriate tests covering any new functionality
  • The documentation has been updated or is unnecessary
  • The changes have been verified
  • New dependencies are appropriate or there were no changes

Includes new or updated dependencies?

YES

* Add PR template
* Add shared CI workflow
* Add .gitignore
* Add Dockerfile
* Add ping and ppod lambda functions
* Add Makefile
* Add Pipfile and requirements.txt for dependencies
* Add README.md
* Add setup.cfg to manage linting
* Add tests for lambda functions

* https://mitlibraries.atlassian.net/browse/ENSY-68
@ehanson8 ehanson8 requested review from hakbailey and zotoMIT May 17, 2022 16:29
* Update Dockerfile
* Update Makefile
* Add unit test
Copy link
Contributor

@hakbailey hakbailey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we only expect this repo to have one lambda function, right? So we can probably remove ping.py (which is mostly useful as an example of how to run different lambda functions from the same repo) and just put ppod.py and its test file in the root directory.

@ehanson8
Copy link
Contributor Author

I had assumed the ping.py and lambdas directory were standard based on your example but I will remove them!

@ehanson8 ehanson8 requested a review from hakbailey May 18, 2022 13:56

bandit:
pipenv run bandit -r lambdas
pipenv run bandit -r ppod.py
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm using a .bandit file in my next PR to skip the test files since this approach will get annoying fast as more files are added

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's possible we may not need to add more files, and can just keep everything in the ppod.py module.

Copy link
Contributor

@hakbailey hakbailey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@ehanson8 ehanson8 merged commit ef74919 into main May 18, 2022
@ehanson8 ehanson8 deleted the ENSY-68-repo-setup branch May 18, 2022 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants