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.

Sign up for GitHub

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

Jump to bottom

Physical resource names are meaningless #1047

Closed
eladb opened this issue Jan 5, 2023 · 1 comment · Fixed by #1078
Closed

Physical resource names are meaningless #1047

eladb opened this issue Jan 5, 2023 · 1 comment · Fixed by #1078
Assignees
@marciocadev
Labels
🐛 bug Something isn't working

Comments

@eladb
Copy link
Contributor

eladb commented Jan 5, 2023

Community Note

Please vote by adding a 👍 reaction to the issue to help us prioritize.
If you are interested to work on this issue, please leave a comment.

I tried this:

I wrote this program:

bring cloud;

new cloud.Bucket() as "bucket1";
new cloud.Bucket() as "bucket2";

And deployed it to AWS.

I expected this:

(from #861)

The names of the resources Wing creates in the cloud are auto-generated and not human friendly. Furthermore, there doesn't seem to be a property that allows them to be set by the developer (I looked through the doc, but didn't see a name field). I'd like at the minimum to be able to specify resource names so I'm not looking in buckets like: terraform-20221125051333963700000005. Ideally there would be some automatic naming too that is more grok-able than a uuid. I'm not sure whether you need a high level entity like a project to help with this, but maybe account-region-project-stage-name.

Instead, this happened:

This was the name of my bucket terraform-20221125051333963700000005

Component:

SDK

Wing Version:

No response

Node.js Version:

No response

Platform(s):

No response

Anything else?

No response
@eladb eladb added the 🐛 bug Something isn't working label Jan 5, 2023
@marciocadev marciocadev mentioned this issue Jan 9, 2023
Merged
@mergify mergify bot closed this as completed in #1078 Jan 22, 2023
mergify bot pushed a commit that referenced this issue Jan 22, 2023
@marciocadev
feat(sdk): meaningful resource name (#1078)
92e49a5 
Trying to give more human friendly names to the aws resources Wing create

Fixes #1047 
Closes #170 

*By submitting this pull request, I confirm that my contribution is made under the terms of the 
[Monada Contribution License](https://docs.winglang.io/terms-and-policies/contribution-license.html)*.
@monadabot
Copy link
Contributor

Congrats! 🚀 This was released in Wing 0.4.118.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@marciocadev marciocadev

Labels
🐛 bug Something isn't working
Projects
Wing
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(sdk): meaningful resource name winglang/wing
3 participants
@eladb @marciocadev @monadabot