[cdk-pipelines/core] Give assets a display name

[rix0rrr]

During cdk deploy and in the pipeline we now have no good way of showing the asset, just a hash.

Much friendlier to users if we should show a display name.

---

This is a 🚀 Feature Request

[bobmoff]

Did this feature die ?

It is a bit confusing to have this..

.. would be awesome to be able to add display name.

[bodokaiser]

@rix0rrr any updates on this issue?

[pfried]

Is there any way (right now) to get better file asset naming?

[clairemr]

+1 feature request, this would be really useful

[sonnenhaft]

+1

[jordanivy]

+1

[martijnburger]

+1

[droewe-reply]

+1

[SQPferrer]

+1

[siggi84]

+1

[github-actions]

This issue has received a significant amount of attention so we are automatically upgrading its priority. A member of the community will see the re-prioritization and provide an update on the issue.

[KevinToala]

+1

[thedevopsguyblog]

+1

[jvjfranca]

+1

[ustulation]

ping... updates pls?

[joshdirkx]

+1

[mccauleyp]

+1

[sgates]

+1

[roey-navina]

+1

[danno-s]

I'd be happy to give implementing this a try. From looking at the code, this would require adding a new field to StackAsset to contain a user-defined name and setting the pipeline's graph node id to it. Something like this:

// In pipeline-graph.ts
// Inside PipelineGraph.publishAsset
const id = stackAsset.assetName ?? stackAsset.assetType === AssetType.FILE
        ? (this.singlePublisher ? 'FileAsset' : `FileAsset${++this._fileAssetCtr}`)
        : (this.singlePublisher ? 'DockerAsset' : `DockerAsset${++this._dockerAssetCtr}`);

As far as I can tell, this would require modifying the schemas in the cloud-assembly-schema package and persisting these names in the asset manifest. With those then we can use them to populate the new field in the StackAsset. However I haven't been able to find where the manifest objects are built before they are persisted.

Does this implementation plan sound reasonable? I'd like some feedback from more experienced people in this project.

[nick-benyo]

Please add?

[eliecer2000]

Is there any way (right now) to get better file asset naming?

Is it possible to group codebuild projects into one?

I say this because I would like a single project that is sending the assets file.

thank you,

[Chrisjw42]

+1

[Belair34]

+9 from my team. This would be quite nice!

[davidmjames]

Another upvote from my team as well.

[avishmehta]

+1

[jcorey-envative]

+1

[dinesh-madhav]

+1 looking to either hide the FileAsset in the pipeline or give meaningful names. If anyone knows how to do the former, it would help me a lot. Thanks

[ilyash-b]

+1

[ustulation]

I might be misremembering but I read somewhere that the tasks in this repo get prioritised based on upvotes on the original (first) post (and not on the progression of the comments). So hopefully everyone +1-ing in the replies are also +1-ing the original post too.

[craigbroadman]

+1

[hakimbho]

+1

[enheit]

+1

[ozerbiber]

+1

[RickKrause]

+1

[melgard]

+1

[LawrenceStanton]

+1

[yasas-mintpay]

+1

[codyataiphone]

+1

[yasas-mintpay]

+1

[devrivne]

+1

[eliecer2000]

Is there any way (right now) to get better file asset naming?

I am working on the improvement of being able to process several assets in a deployment correcting the issue where several codebuilds are created one for each file, which complicates the pipelines, I leave the link of the branch with the correction, I'm still working on sending the PR, but it is functional. I hope it can help.

https://github.com/eliecer2000/aws-cdk/tree/feat/pipeline-assets

[jiayiwang7]

aws/aws-cdk-cli#175