Read mitigator info from Azure #185
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This comment was marked as resolved.
This comment was marked as resolved.
ChrisBeeley
approved these changes
Feb 26, 2025
|
Update: @yiwen-h checked and it's likely to be an authentication issue. I think I just need an ifelse in the |
|
Thank you for joining me on this saga, @yiwen-h. Ready for review (at last). 🥲 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Close #182.
mitigator-lookup.csvfrom Azure, which already uses the new naming convention for frailty mitigators..Renviron.exampleto note the keys required in.Renviron..Renvironinto the README.renv.lockbecause {AzureStor} is now needed (also seemed to clean out some unused packages too).