Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Yacman is a YAML configuration manager. It provides some convenience tools for dealing with YAML configuration files.
Please see this Python notebook for features and usage instructions and this document for API documentation.
How to upgrade to yacman v1.0.0. Yacman v1 provides 2 feature upgrades:
yacman.YAMLConfigManager.from_x(...)
functions, to make it clearer how to
create a new ym
object.The v0.9.3 transition release would has versions, really:
In v1.0.0, FutureYAMLConfigManager will be renamed to YAMLConfigManager and the old stuff will be removed. Here's how to transition your code:
Change from:
from yacman import YAMLConfigManager
to
from yacman import FutureYAMLConfigManager as YAMLConfigManager
Once we switch from v0.9.3
to v1.X.X
, you will need to switch back.
write_lock
or read_lock
from yacman import write_lock, read_lock
Change
with ym as locked_ym:
locked_ym.write()
to
with write_lock(ym) as locked_ym:
locked_ym.write()
More examples:
from yacman import FutureYAMLConfigManager as YAMLConfigManager
data = {"my_list": [1,2,3], "my_int": 8, "my_str": "hello world!", "my_dict": {"nested_val": 15}}
ym = YAMLConfigManager(data)
ym["my_list"]
ym["my_int"]
ym["my_dict"]
# Use in a context manager to write to the file
ym["new_var"] = 15
with write(ym) as locked_ym:
locked_ym.rebase()
locked_ym.write()
with read(ym) as locked_ym:
locked_ym.rebase()
from_{x}
functionsYou can no longer just create a YAMLConfigManager
object directly; now you need to use the constructor helpers.
Examples:
from yacman import FutureYAMLConfigManager as YAMLConfigManager
data = {"my_list": [1,2,3], "my_int": 8, "my_str": "hello world!", "my_dict": {"nested_val": 15}}
file_path = "tests/data/full.yaml"
yaml_data = "myvar: myval"
yacman.YAMLConfigManager.from_yaml_file(file_path)
yacman.YAMLConfigManager.from_yaml_data(yaml_data)
yacman.YAMLConfigManager.from_obj(data)
In the past, you could load from a file and overwrite some attributes with a dict of variables, all from the constructor. Now it would is more explicit:
ym = yacman.YacMan.from_yaml_file(file_path)
ym.update_from_obj(data)
To exppand environment variables in values, use .exp
.
ym.exp["text_expand_home_dir"]
Switch back to:
from yacman import YAMLConfigManager
Some interactive demos
from yacman import FutureYAMLConfigManager as YAMLConfigManager
ym = yacman.YAMLConfigManager(entries=["a", "b", "c"])
ym.to_dict()
ym
print(ym.to_yaml())
ym = YAMLConfigManager(entries={"top": {"bottom": ["a", "b"], "bottom2": "a"}, "b": "c"})
ym
print(ym.to_yaml())
ym = YAMLConfigManager(filepath="tests/data/conf_schema.yaml")
print(ym.to_yaml())
ym
ym = YAMLConfigManager(filepath="tests/data/empty.yaml")
print(ym.to_yaml())
ym = YAMLConfigManager(filepath="tests/data/list.yaml")
print(ym.to_yaml())
ym = YAMLConfigManager(YAMLConfigManager(filepath="tests/data/full.yaml").exp)
print(ym.to_yaml())
ym = YAMLConfigManager(filepath="tests/data/full.yaml")
print(ym.to_yaml(expand=True))
FAQs
A standardized configuration object for reference genome assemblies
We found that yacman demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.