Re:Show HN: oso – Open-Source Policy Engine for Authorization
by samjs on Tuesday July 28, 2020 @08:50PM
(#23982334)
Thanks :)
Right now the idea is you would treat policy files like source code. So any changes should go through CI/CD to be pushed out to production. Any dynamic data can be managed directly through the application, and easily referenced in the policy itself.
I was wondering what is the mechanism for updating/invalidating a policy file across a fleet of servers?