This will permit to manage devcentral configuration easily
Ref T2099
Details
Details
- Reviewers
dereckson - Maniphest Tasks
- T2099: Provision devcentral local configuration
salt docker-002 state.sls_id /srv/phabricator/devcentral/conf/local/local.json roles/paas-docker/containers/phabricator
Diff Detail
Diff Detail
- Repository
- rOPS Nasqueron Operations
- Lint
Lint Errors Severity Location Code Message Error roles/paas-docker/containers/files/phabricator/devcentral/config.json:9 JSON1 Parse Error - Unit
No Test Coverage - Branch
- localConfigDevcentral
- Build Status
Buildable 5781 Build 6063: arc lint + arc unit
Event Timeline
| roles/paas-docker/containers/files/phabricator/devcentral/config.json | ||
|---|---|---|
| 3 | We can reuse all the first line from usual template. | |
| 10 | we can rename the file config.json.jinja (in our repo) to avoid lint | |
| 54 | I would add blank lines for different first words: phabricator.show... | |
| roles/paas-docker/containers/phabricator.sls | ||
| 33 | We can also use get_password here and store the secret under the key "password" on Vault, that's what we do with every other API key. (I see a get_token below, that was historically for Zemke-Rhyne, credentials.get_token is an alias for credentials.get_password) | |
Comment Actions
The configuration option "_comment" is not recognized. It may be misspelled, or it might have existed in an older version of the software. It has no effect, and should be corrected or deleted.
Seems Phabricator doesn't like extra keys.