-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Support multi-resource storage rules deployment. #476
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
Conversation
_.forEach(rulesMap, function(rules, filename) { | ||
utils.logBullet(chalk.cyan('storage:') + ' uploading rules ' + chalk.bold(filename) + '...'); | ||
promises.push(gcp.rules.createRuleset(options.project, rules.files).then(function(rulesetName) { | ||
rules.ruleset = rulesetName; |
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.
What is the purpose of this line?
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.
It persists the created ruleset name in the context
so the release phase can access it when performing a release. See https://github.com/firebase/firebase-tools/pull/476/files#diff-636795e647db388748a86f13457eb5ebR22
No description provided.