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

(13.4.0) INFRASYS-7486 Gives users the option to use autoscaling groups from cloudformation stack #30

Merged
merged 1 commit into from
Jun 30, 2016

Conversation

sbraverman
Copy link
Contributor

No description provided.

@sbraverman sbraverman changed the title [13.3.0] INFRASYS-7486 Gives users the option to use autoscaling groups from cloudformation stack (13.3.0) INFRASYS-7486 Gives users the option to use autoscaling groups from cloudformation stack Jun 23, 2016
self.project = project.replace('-','')
self.buildNum = buildNum
self.buildNum = build_number
Copy link
Contributor Author

Choose a reason for hiding this comment

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

self.buildNum should be snake_case

@sbraverman sbraverman force-pushed the INFRASYS-7486 branch 7 times, most recently from 35ad61a to eb593b5 Compare June 24, 2016 18:25
@sbraverman sbraverman changed the title (13.3.0) INFRASYS-7486 Gives users the option to use autoscaling groups from cloudformation stack (13.4.0) INFRASYS-7486 Gives users the option to use autoscaling groups from cloudformation stack Jun 24, 2016
@sbraverman sbraverman force-pushed the INFRASYS-7486 branch 2 times, most recently from faade63 to 56d5e94 Compare June 24, 2016 20:29
AMI ID
-P PROFILE, --profile PROFILE
Profile name as designated in aws credentials/config
files
-c CONFIG, --config CONFIG
Config file Location, eg.
/opt/License2Deploy/config.yml
-s STACK_NAME, --stack STACK_NAME
Sack name if AutoScaling Group created via CloudFormation
Copy link
Contributor Author

Choose a reason for hiding this comment

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

stack

@nz285
Copy link
Contributor

nz285 commented Jun 30, 2016

+1

@coveralls
Copy link

coveralls commented Jun 30, 2016

Coverage Status

Coverage increased (+0.4%) to 95.185% when pulling 3ce366f on sbraverman:INFRASYS-7486 into 64ff3cc on dandb:master.

@mayn
Copy link
Contributor

mayn commented Jun 30, 2016

+1

return parser.parse_args()

def main(): # pragma: no cover
args = get_args()
SetLogging.setup_logging()
deployObj = RollingDeploy(args.env, args.project, args.buildNum, args.amiID, args.profile, args.config)
deployObj = RollingDeploy(args.env, args.project, args.buildNum, args.amiID, args.profile, args.config, args.stack_name)
Copy link
Contributor

Choose a reason for hiding this comment

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

Did we want to change buildNum here (and in get_args) to build_number to be consistent?

@coveralls
Copy link

coveralls commented Jun 30, 2016

Coverage Status

Coverage increased (+0.4%) to 95.185% when pulling 1b16634 on sbraverman:INFRASYS-7486 into 64ff3cc on dandb:master.

@taoistmath
Copy link
Contributor

One comment otherwise +1

@coveralls
Copy link

coveralls commented Jun 30, 2016

Coverage Status

Coverage increased (+0.4%) to 95.185% when pulling 25fad7b on sbraverman:INFRASYS-7486 into 64ff3cc on dandb:master.

@coveralls
Copy link

coveralls commented Jun 30, 2016

Coverage Status

Coverage increased (+0.4%) to 95.185% when pulling 25fad7b on sbraverman:INFRASYS-7486 into 64ff3cc on dandb:master.

@sbraverman sbraverman merged commit f8fe5b7 into dandb:master Jun 30, 2016
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.

5 participants