-
Notifications
You must be signed in to change notification settings - Fork 1
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
skunk: moves familes to anew centre #788
base: MVL-fudging
Are you sure you want to change the base?
Conversation
app/Console/Commands/ArcSkunk.php
Outdated
$teviot_btg_id = 113; | ||
|
||
$c = Centre::where("id", $teviot_centre_id)->first(); | ||
$reg_associated_with_fam = $c |
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.
This returns an array of registrations belonging to families with the sequences In the filter.
app/Console/Commands/ArcSkunk.php
Outdated
->filter(function ($f) { | ||
return in_array($f->family->centre_sequence, [4, 42, 44, 46, 39, 40, 41, 45]); | ||
}); | ||
$bundles = $reg_associated_with_fam->first()->bundles; |
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.
And because if that, you want to iterate that array of registrations and fetch the reg->bundles for each.
Then iterate the bundles and set the disbursing centre id.
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.
This version just explores the first bundle of the first reg
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
14362054 | Triggered | Generic High Entropy Secret | 60e44cd | app/Http/Controllers/Store/RegistrationController.php | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
No description provided.