You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For secure deployments this will depend on a certificate. The data management application doesn't require a certificate anymore, but this could simply follow the same pattern as the metadata verification script. Would just need to point at a valid certificate. One idea with this is a dummy entity could be created with at least one instance of data. The metadata could allow anyone to find data. Then the principal in the cert doesn't have to be authorized to do anything, it just needs to be valid. Requirements:
puppetize the entity name, version, query, and projection
script can be run by any user
certificate cannot be accessed by user
script execution does not change anything (data or metadata)
everything to setup the script is puppetized
Setup of the metadata and data for this could be left outside of puppet. Puppet would just know the entity name and version to use for the query in the script. Optionally it could create that entity and the data, but that could get more complicated than we probably want to bother with initially, especially since it's likely there would already be an entity that could be used for this without having to create something new.
The text was updated successfully, but these errors were encountered:
For secure deployments this will depend on a certificate. The data management application doesn't require a certificate anymore, but this could simply follow the same pattern as the metadata verification script. Would just need to point at a valid certificate. One idea with this is a dummy entity could be created with at least one instance of data. The metadata could allow
anyone
to find data. Then the principal in the cert doesn't have to be authorized to do anything, it just needs to be valid. Requirements:Setup of the metadata and data for this could be left outside of puppet. Puppet would just know the entity name and version to use for the query in the script. Optionally it could create that entity and the data, but that could get more complicated than we probably want to bother with initially, especially since it's likely there would already be an entity that could be used for this without having to create something new.
The text was updated successfully, but these errors were encountered: