Skip to content

feat(servicecatalog): add ability to set launch Role and deploy with StackSets#15678

Merged
mergify[bot] merged 6 commits intoaws:masterfrom
arcrank:launchrole_stackset_constraint
Jul 22, 2021
Merged

feat(servicecatalog): add ability to set launch Role and deploy with StackSets#15678
mergify[bot] merged 6 commits intoaws:masterfrom
arcrank:launchrole_stackset_constraint

Conversation

@arcrank
Copy link
Copy Markdown
Contributor

@arcrank arcrank commented Jul 20, 2021

Adds 2 constraints, launch role and stackset.
Users can specify a specific role users must assume when launching product.
StackSets deployments allows you to deploy products using Cloudformation StackSets.


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

Aidan Crank added 2 commits July 20, 2021 18:41
…stacksets

Add ability to set launch role (launch role constraint), and configure StackSet deployment
(stackset constraint).
@gitpod-io
Copy link
Copy Markdown

gitpod-io bot commented Jul 20, 2021

@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Jul 20, 2021

Title does not follow the guidelines of Conventional Commits. Please adjust title before merge.

@arcrank arcrank changed the title Launchrole stackset constraint feat(servicecatalog): add ability to set launch role and deploy with stacksets Jul 20, 2021
@arcrank
Copy link
Copy Markdown
Contributor Author

arcrank commented Jul 20, 2021

As always the naming sometimes feels a little weird because we are not using the underlying apis that have sort of misnomer names with 'constraint'.

@arcrank
Copy link
Copy Markdown
Contributor Author

arcrank commented Jul 20, 2021

There is some git churn just from efforts to keep the constrains alphabetized and in order across various files.

Copy link
Copy Markdown
Contributor

@skinny85 skinny85 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! A few API changes are needed before we merge this in.

@mergify mergify bot dismissed skinny85’s stale review July 21, 2021 14:32

Pull request has been modified.

@arcrank arcrank requested a review from skinny85 July 21, 2021 16:54
Copy link
Copy Markdown
Contributor

@skinny85 skinny85 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. Some minor comments.

});

// The execution role deployed in target accounts
const executionRole = iam.Role.fromRoleArn(this, 'ImportedExecutionRole', 'arn:aws:iam::account:role/StackSetExecutionRole');
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

What does it mean that you're using account here, but the accounts property is ['012345678901', '012345678902', '012345678903']?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

this is why I realized using executionRoleName might make more sense, we need the name for the role thats already in the accounts. In another app/stack where those are defined we might have a constructor that creates this role in all accounts but there isn't a way to cleanly/clearly 'import' that here. I just used account since it's a wildcard, but would have maybe made more sense to just use one of the account numbers in the accounts arg.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Yep. Let's switch to a string for the execution Role.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I went with naming it executionRoleName, which immediately gives more info, but also just having 2 args with *Role being different types does not seem ideal.

@mergify mergify bot dismissed skinny85’s stale review July 21, 2021 20:27

Pull request has been modified.

@arcrank arcrank requested a review from skinny85 July 22, 2021 17:16
Copy link
Copy Markdown
Contributor

@skinny85 skinny85 left a comment

Choose a reason for hiding this comment

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

Looks great!


Read more at [Service Catalog Constraints](https://docs.aws.amazon.com/servicecatalog/latest/adminguide/constraints.html).

### Tag update constraint
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

While you're in this area, can you fix the heading for ### Tag Options (it should be an H2, not an H3)?

@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Jul 22, 2021

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@skinny85 skinny85 changed the title feat(servicecatalog): add ability to set launch role and deploy with stacksets feat(servicecatalog): add ability to set launch Role and deploy with StackSets Jul 22, 2021
@aws-cdk-automation
Copy link
Copy Markdown
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject89A8053A-LhjRyN9kxr8o
  • Commit ID: b9e4df6
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@mergify mergify bot merged commit c92548b into aws:master Jul 22, 2021
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Jul 22, 2021

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

TikiTDO pushed a commit to TikiTDO/aws-cdk that referenced this pull request Aug 3, 2021
…StackSets (aws#15678)

Adds 2 constraints, launch role and stackset.
Users can specify a specific role users must assume when launching product.
StackSets deployments allows you to deploy products using Cloudformation StackSets.

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
hollanddd pushed a commit to hollanddd/aws-cdk that referenced this pull request Aug 26, 2021
…StackSets (aws#15678)

Adds 2 constraints, launch role and stackset.
Users can specify a specific role users must assume when launching product.
StackSets deployments allows you to deploy products using Cloudformation StackSets.

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
@arcrank arcrank deleted the launchrole_stackset_constraint branch October 25, 2021 16:40
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