Releases: freakyfelt/could-could
Releases · freakyfelt/could-could
v3.0.2
3.0.2 (2024-09-09)
Bug Fixes
- deps: bump ajv from 8.16.0 to 8.17.1 (#453) (3e9f8ae)
- deps: bump json-logic-js from 2.0.2 to 2.0.5 (#452) (5d36bca)
- deps: bump lru-cache from 10.2.2 to 10.3.0 (#441) (0cba53d)
- deps: bump lru-cache from 10.3.0 to 10.4.0 (#447) (f1195d6)
- deps: bump lru-cache from 10.4.0 to 11.0.0 (#450) (0509e0f)
- deps: bump lru-cache from 11.0.0 to 11.0.1 (#502) (271a404)
v3.0.1
v3.0.0
v2.1.0
v2.0.0-RC1.1
Full Changelog: v2.0.0-RC1...v2.0.0-RC1.1
chore(workflow): drop the broken build step
v2.0.0-RC1
Release candidate for a major simplification of the resolver.
Warning
This is a complete rewrite of the system. I debated adding a compatibility layer; please reach out if this would be useful
New features
- Simplified policy definition that drops built-in support for resources and environments
- Please reach out if a compatibility layer is desired for this
- Allow for pattern matching at the start or end of the action names
- Evaluate deny and allow policies using native JS instead of JsonLogic
- Add initial support for adding new policy documents to the store
- Add caching layers for finding matching policies and compiled evaluators
Migrating
The resolver no longer concerns itself with resource types and environments, meaning implementors will need to create a strategy to load the correct policies into the resolver
{
- "resourceType": "Kitty",
// NOTE: actions are now optional
"actions": ["kitty:pet"],
+ "statement": [
- "definitions": [
- {
- "environment": "production",
- "policies": [
{
"action": "*",
"effect": "allow",
"constraint": true
}
- ]
- }
]
}
Remaining work
- Allow for replacing existing policies in the store
- Allow for dropping policies from the store
- [minor] Organize policies by rough complexity (e.g. evaluate constraints that are purely
false
first as they are much faster to evaluate)
v1.0.0
Initial release of the library