Skip to content

Depend on development version of lambda-builders for dev builds#1111

Merged
sriram-mv merged 4 commits intoaws:dotnet_build_supportfrom
sanathkr:dev-dependencies
Apr 10, 2019
Merged

Depend on development version of lambda-builders for dev builds#1111
sriram-mv merged 4 commits intoaws:dotnet_build_supportfrom
sanathkr:dev-dependencies

Conversation

@sanathkr
Copy link
Contributor

@sanathkr sanathkr commented Apr 9, 2019

Issue #, if available:
During development, we can't easily use development versions of other dependencies such as AWS Lambda Builders.

Description of changes:
In this change, I have separated out dev requirements from prod requirements. For Production, the dependencies are version pinned and pulled from PyPi. For dev requirements, the dependencies are pulled directly from Github source.

I had to remote the extras_requires in setup.py because it did not support installing from Github. Instead I modified the Makefile to pip install these dependencies separately. This is acceptable for development builds.

For production, I concatenate base.txt with prod.txt and use it as the final list of requirements.

Testing:
Following commands worked as expected

  • SAM_CLI_DEV=1 pip install -e .
  • pip install -e .
  • make init

Checklist:

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@@ -1,5 +1,7 @@
init:
SAM_CLI_DEV=1 pip install -e '.[dev]'
SAM_CLI_DEV=1 pip install -e .
Copy link
Contributor

@sriram-mv sriram-mv Apr 9, 2019

Choose a reason for hiding this comment

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

we have silently changed the contract of make init now, to always build the latest from lambda-builders in develop. this can have issues when there is a breaking change in lambda builders develop, but the corresponding component to fix sam cli has not yet been merged.

we need to keep this in mind and fix it.

@sriram-mv sriram-mv changed the base branch from develop to dotnet_build_support April 10, 2019 16:39
@sriram-mv sriram-mv merged commit 7e9de79 into aws:dotnet_build_support Apr 10, 2019
sanathkr added a commit to sanathkr/aws-sam-cli that referenced this pull request Apr 15, 2019
sanathkr added a commit that referenced this pull request Apr 15, 2019
sriram-mv pushed a commit that referenced this pull request Apr 16, 2019
* chore(version): set 0.14.3.dev1 version (#1112) (#1113)

* Depend on development version of lambda-builders for dev builds (#1111)

* Depend on development version of lambda-builders for dev builds

* Adding prod.txt to manifest

* Splitting dev and tool dependencies

* fix(build): Resolve path after .aws-sam is created (#1110)

* fix(build): Resolve path after .aws-sam is created

* fix: build (make pr)

* Design and implementation for producing debug build artifacts (#1095)

* design: Initial Design for producing debug artifacts

* initial implementation

* Adding unit tests

* Integration test with debug build mode

* Adjust Design doc and add keyword arg to a call

* fix(dotnet): init template fixes (#1117)

* chore(version): set 0.15.0 (#1125)

* Revert "Depend on development version of lambda-builders for dev builds (#1111)" (#1128)

This reverts commit 7e9de79.

* Bumping to Lambda Builders 0.3.0 (#1129)

Bumping to Lambda Builders 0.3.0

* fix(func-tests): add dependency manager param (#1130)
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