pegleg/pegleg/engine/util
Phil Sphicas 417975b596 Uniquely name managed documents
When pegleg wraps documents, it uses the original document name as the
name of the managed document. This often results in duplicate documents
(i.e. identical in name and schema). For example, it is expected to have
identically named deckhand document pairs: Certificate & CertificateKey;
CertificateAuthority & CertificateAuthorityKey; PublicKey & PrivateKey.

However, this could also occur for unrelated document types that happen
to have the same name, and generally defeats the principle that each
document is identified by a schema top-level key and the metadata.name.

This change uses a combination of the original document schema and name
to build the name of the pegleg/PeglegManagedDocument/v1.

Change-Id: Iab186ae7e9d24a30cb413be89a17fad960e10bea
2020-04-20 18:45:55 +00:00
..
__init__.py pki: Port Promenade's PKI catalog into Pegleg 2019-01-15 13:29:21 -06:00
catalog.py Standardize Pegleg code with YAPF 2019-07-25 17:28:18 +00:00
cryptostring.py Add profiles to passphrase catalog 2019-09-24 16:19:36 +00:00
deckhand.py Standardize Pegleg code with YAPF 2019-07-25 17:28:18 +00:00
definition.py Standardize Pegleg code with YAPF 2019-07-25 17:28:18 +00:00
encryption.py Standardize Pegleg code with YAPF 2019-07-25 17:28:18 +00:00
files.py Set a fixed order in which data is dumped to YAML files 2019-08-02 18:33:26 +00:00
git.py Handle Pegleg-generated commits in deployment data 2019-09-12 13:38:54 -05:00
pegleg_managed_document.py Uniquely name managed documents 2020-04-20 18:45:55 +00:00
pegleg_secret_management.py bugfix for global encrypt/decrypt 2019-10-02 19:13:33 +00:00
shipyard_helper.py Add deployment_data to rendered docs 2019-09-17 12:39:33 +00:00