Skip to content
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.

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

Upper case the values for datapipeline status #1110

Merged
merged 1 commit into from
Jan 27, 2015

Conversation

jamesls
Copy link
Member

@jamesls jamesls commented Jan 27, 2015

They need to match the status given in the response
output.

Before:

$ aws datapipeline list-runs --pipeline-id df-id --status finished
       Name                                                Scheduled Start      Status
       ID                                                  Started              Ended
---------------------------------------------------------------------------------------------------

After:

$ aws datapipeline list-runs --pipeline-id df-id --status finished
       Name                                                Scheduled Start      Status
       ID                                                  Started              Ended
---------------------------------------------------------------------------------------------------
   1.  CliActivity                                         2015-01-27T20:32:46  FINISHED
       @CliActivity_2015-01-27T20:32:46                    2015-01-27T20:32:49  2015-01-27T20:35:27

   2.  Ec2Instance                                         2015-01-27T20:32:46  FINISHED
       @Ec2Instance_2015-01-27T20:32:46                    2015-01-27T20:32:50  2015-01-27T20:37:29

cc @kyleknap @danielgtaylor

They need to match the status given in the response
output.
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.01%) to 91.76% when pulling 3852678 on jamesls:fix-datapipeline-status into 3ac9eb7 on aws:develop.

@jamesls
Copy link
Member Author

jamesls commented Jan 27, 2015

Not sure what the deal is with coveralls. I didn't add any new lines of code, I just modified existing lines as well as modified their corresponding tests. Not sure why it's reporting a coverage drop.

@kyleknap
Copy link
Contributor

Yeah, its fine. I do not know how it can drop. Looks good. 🚢

@jamesls jamesls merged commit 3852678 into aws:develop Jan 27, 2015
thoward-godaddy pushed a commit to thoward-godaddy/aws-cli that referenced this pull request Feb 12, 2022
* chore(version): set 0.14.3.dev1 version (aws#1112) (aws#1113)

* Depend on development version of lambda-builders for dev builds (aws#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 (aws#1110)

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

* fix: build (make pr)

* Design and implementation for producing debug build artifacts (aws#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 (aws#1117)

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

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

This reverts commit 7e9de790e23791ba176faff2030286db4007e503.

* Bumping to Lambda Builders 0.3.0 (aws#1129)

Bumping to Lambda Builders 0.3.0

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

3 participants