We should add support for encrypting env vars into taskcluster-client, both the node.js client and the python client. See bug 1140046, and docs: http://docs.taskcluster.net/docker-worker/ And make sure we implement the most recent iteration. (probably wait for bug 1140046)
Component: TaskCluster → General
Product: Testing → Taskcluster
Comment on attachment 8640011 [details] [review] Add encryption support for the python version Looks great. As mentioned in the pr comments, the taskcluster client uses camel casing as a conscious choice. Please make sure that your functions, parameters and locals use camel casing. There are a couple of name changes that I'd like to see as well. Thanks for writing tests, it's really great to see. Having companion decryption functions in the library would be nice to see. Is it a huge amount of work to add decryption? I'd like for both consumers and also so that the unit tests can ensure that our encrypted env vars are valid and not just a random number generator. Please r? me again when you've addressed the comments.
Comment on attachment 8640011 [details] [review] Add encryption support for the python version Take 2
Comment on attachment 8640011 [details] [review] Add encryption support for the python version Assuming r+ because it was merged
Attachment #8640011 - Flags: review?(jhford) → review+
Assumption correct! Released as version 0.0.23
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Assignee: nobody → rail
Component: Client Libraries → Services
Product: Taskcluster → Taskcluster
You need to log in before you can comment on or make changes to this bug.