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

Multiple Assets In the same stack #706

Closed
sentient-jbreindel opened this issue Sep 13, 2018 · 2 comments · Fixed by #725
Closed

Multiple Assets In the same stack #706

sentient-jbreindel opened this issue Sep 13, 2018 · 2 comments · Fixed by #725
Labels
bug This issue is a bug.

Comments

@sentient-jbreindel
Copy link

Whenever I try to create a stack with multiple assets I receive the following error when I run cdk synth:

Error: There is already a Construct with name 'AssetBucket' in ApiStack [ApiStack]
    at ApiStack.addChild (/git/project/node_modules/@aws-cdk/cdk/lib/core/construct.js:287:19)
    at new Construct (/git/project/node_modules/@aws-cdk/cdk/lib/core/construct.js:38:20)
    at new BucketRef (/git/project/node_modules/@aws-cdk/aws-s3/lib/bucket.js:30:9)
    at new ImportedBucketRef (/git/project/node_modules/@aws-cdk/aws-s3/lib/bucket.js:519:9)
    at Function.import (/git/project/node_modules/@aws-cdk/aws-s3/lib/bucket.js:46:16)
    at new Asset (/git/project/node_modules/@aws-cdk/assets/lib/asset.js:48:42)
    at new ZipDirectoryAsset (/git/project/node_modules/@aws-cdk/assets/lib/asset.js:95:9)
    at new ApiStack (/git/project/index.js:100:24)
    at new App (/git/project/index.js:187:5)
    at Object.<anonymous> (/git/project/index.js:191:22)

I noticed that when defining a new asset the bucket is always imported with the same name. I think this may be the offending line.

@eladb
Copy link
Contributor

eladb commented Sep 13, 2018

You are right. It's a 🐛

The BucketRef is anchored at parent and should be anchored at this.

this.bucket = s3.BucketRef.import(parent, 'AssetBucket', {

should be changed to:

this.bucket = s3.BucketRef.import(this, 'AssetBucket', {

Should be an easy fix.

As a workaround, you can wrap your asset in a construct so it will be namespaced:

class MyAsset extends cdk.Construct {
  public readonly asset: Asset;
  constructor(parent: cdk.Construct, id: string, props: AssetProps) {
    super(parent, id);

    this.asset = new Asset(this, 'Asset', props);
  }
}

Then, you can use it:

const asset1 = new MyAsset(this, 'Asset1', { /* asset properties */ }).asset;
const asset2 = new MyAsset(this, 'Asset2', { /* asset properties */ }).asset;

@eladb eladb added the bug This issue is a bug. label Sep 13, 2018
@sentient-jbreindel
Copy link
Author

Perfect thank you for the workaround!

rix0rrr pushed a commit that referenced this issue Sep 17, 2018
Fixed by attaching the imported bucket to the Asset object instead
of the Asset object's parent.

Fixes #706.
rix0rrr added a commit that referenced this issue Sep 17, 2018
Fixed by attaching the imported bucket to the Asset object instead
of the Asset object's parent.

Fixes #706.
eladb pushed a commit that referenced this issue Sep 20, 2018
__NOTICE__: This release includes a framework-wide [__breaking
change__](#712) which changes the type
of all the string resource attributes across the framework. Instead of using
strong-types that extend `cdk.Token` (such as `QueueArn`, `TopicName`, etc), we
now represent all these attributes as normal `string`s, and codify the tokens
into the string (using the feature introduced in [#168](#168)).

Furthermore, the `cdk.Arn` type has been removed. In order to format/parse ARNs,
use the static methods on `cdk.ArnUtils`.

See motivation and discussion in [#695](#695).

* **cfn2ts:** use stringified tokens for resource attributes instead of strong types ([#712](#712)) ([6508f78](6508f78)), closes [#518](#518) [#695](#695) [#744](#744)
* **aws-dynamodb:** Attribute type for keys, changes the signature of the `addPartitionKey` and `addSortKey` methods to be consistent across the board. ([#720](#720)) ([e6cc189](e6cc189))
* **aws-codebuild:** fix typo "priviledged" -> "privileged

* **assets:** cab't use multiple assets in the same stack ([#725](#725)) ([bba2e5b](bba2e5b)), closes [#706](#706)
* **aws-codebuild:** typo in BuildEnvironment "priviledged" -> "privileged     ([#734](#734)) ([72fec36](72fec36))
* **aws-ecr:** fix addToResourcePolicy ([#737](#737)) ([eadbda5](eadbda5))
* **aws-events:** ruleName can now be specified ([#726](#726)) ([a7bc5ee](a7bc5ee)), closes [#708](#708)
* **aws-lambda:** jsii use no long requires 'sourceAccount' ([#728](#728)) ([9e7d311](9e7d311)), closes [#714](#714)
* **aws-s3:** remove `policy` argument ([#730](#730)) ([a79190c](a79190c)), closes [#672](#672)
* **cdk:** "cdk init" java template is broken ([#732](#732)) ([281c083](281c083)), closes [#711](#711) [aws/jsii#233](aws/jsii#233)

* **aws-apigateway:** new API Gateway Construct Library ([#665](#665)) ([b0f3857](b0f3857))
* **aws-cdk:** detect presence of EC2 credentials ([#724](#724)) ([8e8c295](8e8c295)), closes [#702](#702) [#130](#130)
* **aws-codepipeline:** make the Stage insertion API in CodePipeline more flexible ([#460](#460)) ([d182818](d182818))
* **aws-codepipeline:** new "Pipeline#addStage" convenience method ([#647](#647)) ([25c9fa0](25c9fa0))
* **aws-rds:** add support for parameter groups ([#729](#729)) ([2541508](2541508)), closes [#719](#719)
* **docs:** add documentation for CDK toolkit plugings ([#733](#733)) ([965b918](965b918))
* **dependencies:** upgrade to [jsii 0.7.6](https://github.com/awslabs/jsii/releases/tag/v0.7.6)
eladb pushed a commit that referenced this issue Sep 20, 2018
* v0.9.2

__NOTICE__: This release includes a framework-wide [__breaking
change__](#712) which changes the type
of all the string resource attributes across the framework. Instead of using
strong-types that extend `cdk.Token` (such as `QueueArn`, `TopicName`, etc), we
now represent all these attributes as normal `string`s, and codify the tokens
into the string (using the feature introduced in [#168](#168)).

Furthermore, the `cdk.Arn` type has been removed. In order to format/parse ARNs,
use the static methods on `cdk.ArnUtils`.

See motivation and discussion in [#695](#695).

* **cfn2ts:** use stringified tokens for resource attributes instead of strong types ([#712](#712)) ([6508f78](6508f78)), closes [#518](#518) [#695](#695) [#744](#744)
* **aws-dynamodb:** Attribute type for keys, changes the signature of the `addPartitionKey` and `addSortKey` methods to be consistent across the board. ([#720](#720)) ([e6cc189](e6cc189))
* **aws-codebuild:** fix typo "priviledged" -> "privileged

* **assets:** cab't use multiple assets in the same stack ([#725](#725)) ([bba2e5b](bba2e5b)), closes [#706](#706)
* **aws-codebuild:** typo in BuildEnvironment "priviledged" -> "privileged     ([#734](#734)) ([72fec36](72fec36))
* **aws-ecr:** fix addToResourcePolicy ([#737](#737)) ([eadbda5](eadbda5))
* **aws-events:** ruleName can now be specified ([#726](#726)) ([a7bc5ee](a7bc5ee)), closes [#708](#708)
* **aws-lambda:** jsii use no long requires 'sourceAccount' ([#728](#728)) ([9e7d311](9e7d311)), closes [#714](#714)
* **aws-s3:** remove `policy` argument ([#730](#730)) ([a79190c](a79190c)), closes [#672](#672)
* **cdk:** "cdk init" java template is broken ([#732](#732)) ([281c083](281c083)), closes [#711](#711) [aws/jsii#233](aws/jsii#233)

* **aws-apigateway:** new API Gateway Construct Library ([#665](#665)) ([b0f3857](b0f3857))
* **aws-cdk:** detect presence of EC2 credentials ([#724](#724)) ([8e8c295](8e8c295)), closes [#702](#702) [#130](#130)
* **aws-codepipeline:** make the Stage insertion API in CodePipeline more flexible ([#460](#460)) ([d182818](d182818))
* **aws-codepipeline:** new "Pipeline#addStage" convenience method ([#647](#647)) ([25c9fa0](25c9fa0))
* **aws-rds:** add support for parameter groups ([#729](#729)) ([2541508](2541508)), closes [#719](#719)
* **docs:** add documentation for CDK toolkit plugings ([#733](#733)) ([965b918](965b918))
* **dependencies:** upgrade to [jsii 0.7.6](https://github.com/awslabs/jsii/releases/tag/v0.7.6)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants