-
Notifications
You must be signed in to change notification settings - Fork 8
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
Merge develop into main to push some new features #669
base: main
Are you sure you want to change the base?
Conversation
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
- | - | SMTP credentials | 3790c89 | ops/alpha-deploy.tmpl.yaml | View secret |
8978162 | Triggered | Username Password | 238a8b5 | .env | View secret |
8978162 | Triggered | Username Password | 29e5cae | .env | 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 secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- 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.
This commit will replace all instances of AdminSet.find_or_create_default_admin_set_id with Hyrax::AdminSetCreateService.find_or_create_default_admin_set.id.to_s because the former was deprecated.
I75 cleanup upgrade
This commit will fix various specs that were failing because of the Ruby 3.2.2 upgrade. At this point there should only be 4 failures left. ``` 879 examples, 4 failures, 38 pending Failed examples: rspec ./spec/models/bulkrax/pbcore_xml_entry_spec.rb:92 rspec ./spec/models/bulkrax/pbcore_xml_entry_spec.rb:87 rspec ./spec/models/bulkrax/pbcore_xml_entry_spec.rb:169 rspec ./spec/services/aapb/batch_ingest/csv_reader_spec.rb:30 ```
This commit pulls in the changes for the PbcoreXMLEntry spec from develop that passes.
In a previous commit where we removed support for rails 5.1 we forgot to copy over the view directory.
…97-bulkrax-meets-valkyrie
🧹 restore view directory
This work is still in progress. The valkyrie config file is commented out until we receive code for implementing adapters. We are using the object_factory config to utilize Valkyrie::ObjectFactory and lastly we added some changed to avoid errors when running an import. Issue: - scientist-softserv#97 Co-Authored-By: Kirk Wang <[email protected]> Co-Authored-By: LaRita Robinson <[email protected]>
…A/ams into ruby_tuesday_3.2_edition
adding new annotation as a method here too
adding ams1_legacy_metadata here too
Update annotation_types.yml
Also, * Adds conditionals to only include Bulkrax transaction steps if Bulkrax is enabled. * Use work_resource.create_with_bulkrax_behavior Container if enabled. * Use change_set.create_work if not enabled. * Ignores local Sony Ci and Kubeconfig credential files based on default naming conventions and locations Co-authored-by: Benjamin Kiah Stroud <[email protected]>
…ia Type (#922) Refactors some one-type scripts into more re-usable batch processing methods that can be run from the ruby console or CLI. * Delete Assets by ID list from file. * Delete Physical Instantiations by Media Type and IDs from file. * Change Media Type for instantiations by IDs from file.
…for redis to get the aof file into memory
dont-rush-redis-healthchecks
No description provided.