{ "id": "105715", "key": "TIMOB-11902", "fields": { "issuetype": { "id": "2", "description": "A new feature of the product, which has yet to be developed.", "name": "New Feature", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [], "resolution": null, "resolutiondate": null, "created": "2012-11-30T00:55:00.000+0000", "priority": { "name": "Low", "id": "4" }, "labels": [ "cb-tooling", "titaniumlib" ], "versions": [ { "id": "13505", "description": "Release 3.0.0", "name": "Release 3.0.0", "archived": true, "released": true, "releaseDate": "2012-12-14" } ], "issuelinks": [ { "id": "58209", "type": { "id": "10003", "name": "Relates", "inward": "relates to", "outward": "relates to" }, "inwardIssue": { "id": "171283", "key": "DAEMON-243", "fields": { "summary": "Create titaniumlib with tiapp.xml parsing, sdk and module detection logic", "status": { "description": "The issue is open and ready for the assignee to start work on it.", "name": "Open", "id": "1", "statusCategory": { "id": 2, "key": "new", "colorName": "blue-gray", "name": "To Do" } }, "priority": { "name": "Critical", "id": "1" }, "issuetype": { "id": "7", "description": "gh.issue.story.desc", "name": "Story", "subtask": false } } } }, { "id": "29825", "type": { "id": "10003", "name": "Relates", "inward": "relates to", "outward": "relates to" }, "inwardIssue": { "id": "116453", "key": "TIMOB-14384", "fields": { "summary": "TiAPI: Enable secure storage of sensitive tiapp.xml properties", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "priority": { "name": "Critical", "id": "1" }, "issuetype": { "id": "2", "description": "A new feature of the product, which has yet to be developed.", "name": "New Feature", "subtask": false } } } } ], "assignee": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "updated": "2020-03-06T21:36:30.000+0000", "status": { "description": "The issue is open and ready for the assignee to start work on it.", "name": "Open", "id": "1", "statusCategory": { "id": 2, "key": "new", "colorName": "blue-gray", "name": "To Do" } }, "components": [ { "id": "13103", "name": "CLI", "description": "Node-based command line interface" } ], "description": "Similar to ANT, we'd like a mechanism whereby individuals can supply a separate file for build-time properties and these would replace variables during the compilation step.\r\n\r\nA good use case for this might be the secret keys in ACS. We'd like to not store them in tiapp.xml, and instead have a separate build.properties file that contains the key/value pairs. This file would then get a .gitignore, so we don't accidentally check it into source control.\r\n\r\nAn example:\r\n\r\n{panel:title=tiapp.xml}\r\n$\\{acs-oauth-secret-production\\}\r\n{panel}\r\n\r\n{panel:title=build.properties}\r\nacs-oauth-secret-production=XXYYZZ\r\n{panel}\r\n\r\nThere would need to be some way to indicate which file contained the properties.", "attachment": [], "flagged": false, "summary": "Add ability to provide build-time properties for projects in a separate file", "creator": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "ingo", "key": "ingo", "displayName": "Ingo Muschenetz", "active": true, "timeZone": "America/Los_Angeles" }, "environment": null, "comment": { "comments": [ { "id": "394469", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "This is brilliant!\r\n\r\nWe currently required users to pass in their provisioning profile uuid, developer cert name, and dist cert name to the build command. It rarely changes, so it would be better to put this in a file. We can't use the {{tiapp.xml}} since apps could be developed by a team of people, each with different developer certs and such.\r\n\r\nI don't like the idea of a key/value file. I think it needs to be hierarchical. I don't think JSON would work since it doesn't allow comments and requires extra work to define a schema.\r\n\r\nIf we had a {{user.xml}} that shared a similar structure to the {{tiapp.xml}}, then we could {{.gitignore}} that one file and essentially have the build \"merge\" the {{user.xml}} on top of the {{tiapp.xml}}.\r\n\r\nTo make managing this file easier, we could whip up a quick {{ti setup}} screen for selecting their provisioning profile uuid, etc.\r\n\r\nStudio would have to get creative. It could simply load the {{user.xml}} in the tiapp editor, but with a much looser schema.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2016-08-26T04:37:42.000+0000", "updated": "2016-08-26T04:37:42.000+0000" } ], "maxResults": 1, "total": 1, "startAt": 0 } } }