-
Notifications
You must be signed in to change notification settings - Fork 116
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Store extension install report as JSON (#796)
Store the extension install report as JSON. This makes it consistent across all integrations. Closes #783 I've picked this up earlier than originally planned, because the Ruby 3.1.0 release changes some things with YAML that makes it more difficult to maintain across different Ruby versions. I'd rather remove as much as YAML backwards compatibility logic as possible and use JSON instead that does not have the same issue. `YAML.load` now calls `YAML.safe_load` by default in Ruby 3.1.0. `YAML.safe_load` isn't implemented in all the Ruby versions we still support, so we can't switch to that method call, and calling `YAML.load` will cause differences between Ruby versions. I looked into making parsing YAML standardized for all cases we use it, but different options are needed for `YAML.load` which would default the purpose. Instead I think removing all uses of YAML, except the config file, is the best way to go. The only other use I can find is the `agent.yml` file, we can also convert that to JSON.
- Loading branch information
Showing
6 changed files
with
15 additions
and
22 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
--- | ||
bump: "patch" | ||
type: "change" | ||
--- | ||
|
||
Store the extension install report as JSON, instead of YAML. Reduces internal complexity. |
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 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 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 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