DefangLabs / DefangLabs/defang
GCP: long project names may cause issues with subnet naming
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 166
- Forks
- 24
- Avg merge
- 10h 8m
- Merged PRs (30d)
- 33
Description
I received this error when deploying sample sample-django-channels-redis-postgres :
error: could not make instance of 'gcp:compute/subnetwork:Subnetwork': name 'sample-django-channels-redis-postgres-template-shared-subnet-' plus 7 random chars is longer than maximum length 63
Any long project name would cause this. we should be able to validate for users before deployment actually occurs.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the GCP deployment code that constructs subnetwork names and the validation entry point used before deployment. Reproduce the failure with a project name like sample-django-channels-redis-postgres, then verify that an overlong name is rejected before deployment with a clear error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, go
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100