-
Notifications
You must be signed in to change notification settings - Fork 49
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
bucketName property is not honored, not working #17
Comments
Hi @kling-appfire ... the So if you'd like to have your bucket name set, you could do a remove then deploy again with the If it doesn't let me know, I'll keep this issue open for ya! 😊 |
Got it working! Not quite sure how. There were several issue related to having a 'stale' .serverless folder. We've been switching between .env (profiles) and there are apparently some stored settings in .serverless that need to be cleared out related to bucketnames. Replicate by running with one bucketName, then change the bucketName w/same .serverless and it will not create a new bucket. |
I am not able to set bucketName to be customized something like |
I am still able to setup bucketName but I noted that if we use full domain name i.e. my-app.domain.com then we will have an error relate to CloudFront distribution. BTW, I have written this post to describe how to use the serverless component to deploy multiple stages/environments. We are using in production and have no issue so far. |
Thank you for the post. In my case, I used serverless website component, which do not have provider as aws in serverless.yml, hence I can't use resources>Resources> Bucket etc and I am deploying using just serverless, not serverless deploy. |
I am on a similar situation. For some reason I can not understand it allways tries to generate the same: {
"region": "us-east-1",
"privateZone": false,
"domain": "danielo.es",
"subdomains": [
{
"domain": "pento.danielo.es",
"type": "awsS3Website",
"s3BucketName": "pento"
}
]
} Subdomain is correct, but buketName is not, domain is not...
|
I am in a similar situation I am attempting to do:
|
Given the following website serverless.yml the bucket is named a random system assigned GUID name regardless of if the bucketName property is there or not.
`
name: my.domain.com
stage: local
website:
component: '@serverless/website'
inputs:
code:
src: client/dist
hook: domain=my.domain.com npm run clean:build
region: us-east-1
bucketName: local.my.domain.com-specialbucketname123
env:
API_URL: https://my.domain.com
STAGE: local
`
Tried:
The text was updated successfully, but these errors were encountered: