Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Datum to reference another Datum datum path #19

Open
gaelcolas opened this issue Jan 3, 2018 · 1 comment
Open

Datum to reference another Datum datum path #19

gaelcolas opened this issue Jan 3, 2018 · 1 comment
Milestone

Comments

@gaelcolas
Copy link
Owner

Some Config Data should not or cannot be saved at the correct place of the hierarchy (i.e. a config file, or certificate used as a parameter to a Configuration):

MyResource:
  CN: MyCN
  Certificate: "<blob of file content>"

Managing the certificate in-line is not convenient, the file should probably be in it's own 'provider' or mounted somewhere else in the Datum Tree ($Datum.Files.certificates.MyResourceCert).

That means the data structure for MyResource should have the certificate file 'linked' to the Certificate key of the config Data, like so (in a similar pattern that of Secure Datum):

MyResource:
  CN: MyCN
  Certificate: "[REF=[Files\certificates\MyResourceCert]]"

Now, during a lookup $Node 'MyResource', Datum should resource the following hashtable, resolving under the hood the file content (or following what looks like a redirection):

@{
    CN = 'MyCN'
    Certificate = 'blob of file content'
}
@gaelcolas gaelcolas added this to the v1.0 milestone Jan 3, 2018
@gaelcolas
Copy link
Owner Author

Until it's integrated natively, I've documented how to do this here: https://github.com/gaelcolas/Datum/blob/master/docs/Datum_Redirections.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant