Change Details

See T13542. --- Stuff Piledriver could use: - Almanac search by property and/or property value, i.e. "find any device with property X" or "find any device with property X set to value Y". This doesn't have to be high-performance or well-indexed. Vaguely nice to have: - See related T13220. API-level support for a "viewer()" policy. The default policy for Almanac devices is "Administrators", and a bot user may not satisfy this. Templates could configure an explicit policy, but "viewer()" would be a reasonable default. Piledriver can figure out the acting user PHID with `user.whoami` and effect this policy, but this could be cleaner with "viewer()".

See T13542. --- Stuff Piledriver could use: - Almanac search by property and/or property value, i.e. "find any device with property X" or "find any device with property X set to value Y". This doesn't have to be high-performance or well-indexed. - See PHI1331. It would be nice to have better support for a "destroyed" lifecycle stage in Almanac. Vaguely nice to have: - See related T13220. API-level support for a "viewer()" policy. The default policy for Almanac devices is "Administrators", and a bot user may not satisfy this. Templates could configure an explicit policy, but "viewer()" would be a reasonable default. Piledriver can figure out the acting user PHID with `user.whoami` and effect this policy, but this could be cleaner with "viewer()".

See T13542. --- Stuff Piledriver could use: - Almanac search by property and/or property value, i.e. "find any device with property X" or "find any device with property X set to value Y". This doesn't have to be high-performance or well-indexed. - See PHI1331. It would be nice to have better support for a "destroyed" lifecycle stage in Almanac. Vaguely nice to have: - See related T13220. API-level support for a "viewer()" policy. The default policy for Almanac devices is "Administrators", and a bot user may not satisfy this. Templates could configure an explicit policy, but "viewer()" would be a reasonable default. Piledriver can figure out the acting user PHID with `user.whoami` and effect this policy, but this could be cleaner with "viewer()".