-
Notifications
You must be signed in to change notification settings - Fork 902
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
Hosting deploy migration to apiv2, typescript, project-scoped #3989
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but question about ES Lint exceptions before approval.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM after typing options
/** | ||
* Prepare creates versions for each Hosting site to be deployed. | ||
*/ | ||
export async function prepare(context: any, options: any): Promise<void> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use the options type from options.ts so these warnings are silenced?
Derp, I didn't realize automerge was on - feel free to make the options switch another time (or we can try to do it as a LSC) |
Description
I've updated the hosting deploy path to be:
This helpfully fixes the issue where a deploy can go to a site not on the same project, which is definitely not intended.
Fixes #2558
Scenarios Tested
firebase deploy --only hosting
firebase hosting:channel:deploy staging