So there are two things that stick out.

1. Regarding us calling the preparing template call ourselves rather than letting it be handled, we call it and resolve the path ourselves in constructor, the tests fail if we don't, so either those need to be fixed. Is there a specific example for where this would fail that I can use to build off of?
2. Regarding how to verify the multiple stacks and finding the other template file as I mentioned above. I'm still working on this.

1. Regarding us calling the preparing template call ourselves rather than letting it be handled, we call it and resolve the path ourselves in constructor, the tests fail if we don't, so either those need to be fixed. Is there a specific example for where this would fail that I can use to build off of?

Fail how?

Considering the NestedStacks work the same, and their tests work fine, I think there's something wrong with the current implementation.

I think _prepareTemplateAsset() might not be the correct function to override here. Look when it is invoked.

I think you might need to hook up into the synthesis step in a different way (prepare() maybe?).

@skinny85 this was the simplest form I could get this into, hopefully there isn't some JSII compatibility issue with this sort of interface check.

Wasn't sure if the renaming appropriate, let me know if there is better terminology we can use.

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).

AWS CodeBuild CI Report

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

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

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).

Can someone point me to the documentation or examples of how we can use this product stack to create Service Catalog product? We're itching to use this functionality but struggling

@shahbhavik01 does this help? https://docs.aws.amazon.com/cdk/api/latest/docs/aws-servicecatalog-readme.html#creating-a-product-from-a-stack

@shahbhavik01 does this help? https://docs.aws.amazon.com/cdk/api/latest/docs/aws-servicecatalog-readme.html#creating-a-product-from-a-stack

Yes! Thank you @skinny85

@skinny85 @arcrank What's the correct way to reference parameters as value within the productStack? I'm trying to do something like:

        const natGateways = new cdk.CfnParameter(this, "natGateways", {
          type: "Number",
          description: "The number of Nat Gateways to attach",
        });

And then:

        const vpc = new ec2.Vpc(this, "threeTierVPC", {
          cidr: "10.0.0.0/16", 
          natGateways: natGateways.valueAsNumber,
        });

Both within the product stack.

This however doesn't create a Nat Gateway even if I pass two when deploying the product.
Can we not use any higher level constructs within the product stack? Are there other more complex examples you know of besides the s3 example that use the productStack to create a service catalog product?

@shahbhavik01 can you show your entire CDK code, and the resulting template that's generated? (You will find it in the cdk.out directory)

@skinny85 Yes. See attached.

service_catalog_files.zip

The goal we're working on is to create a set of products under one portfolio.

Attached is the code containing the product. I have added my bin/ lib/ and cdk.out folders.

Thanks, I am able to replicate. I think this partly an issue with passing in tokens to the vpc construct, as it does conditional generation of underlying resources based on that, but need to confirm this behavior.

@arcrank Thank you for looking into it. If I get rid of the conditional VPC resources and then create each resource individually, would this work? Does the code look ok otherwise? Is this how you intended the use of service catalog product on CDK?

@shahbhavik01, putting CfnParameters in the ProductStack should and does work when it's mapping to a field in the template. The crux of issue is that it's not really a CfnParameter for the template, but rather a functional part of cdk code, that abstracts away generating part of a template. In this case I actually think the VPC construct should be checking if Token is resolvable and throwing an error. While this is not ideal, it should at least fail fast. So yes, if you for example have all of the resources added and are using a CfnParameter for a cidr mask value it will work.

You bring up a good point that we definitely want to consider going forward, as more powerful abstractions for resources will not be available to product stack, when a construct or resources represents a cdk function that can map to n underlying resources depending on the configuration. We will definitely be looking into this going forward.

Thank you for the detailed explanation. I will keep that in mind and develop accordingly.