Project

General

Profile

Actions

Feature #14554

closed

[Config] Config files deployment

Added by Michał Kłobukowski about 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-
Release:
Release relationship:
Auto

Description

Config files deployment should be automated.

- config.json (see https://dev.arvados.org/issues/13817)
- vocabulary.json (see https://dev.arvados.org/issues/14393)


Related issues

Blocks Arvados Workbench 2 - Story #14393: Provide support for using controlled vocabulary/terminology service when setting properties on collectionsClosedMichał Kłobukowski

Actions
Actions #1

Updated by Michał Kłobukowski about 4 years ago

  • Related to Story #14393: Provide support for using controlled vocabulary/terminology service when setting properties on collections added
Actions #2

Updated by Michał Kłobukowski about 4 years ago

  • Description updated (diff)
Actions #3

Updated by Michał Kłobukowski about 4 years ago

  • Description updated (diff)
Actions #4

Updated by Michał Kłobukowski about 4 years ago

  • Description updated (diff)
Actions #5

Updated by Michał Kłobukowski about 4 years ago

  • Related to deleted (Story #14393: Provide support for using controlled vocabulary/terminology service when setting properties on collections)
Actions #6

Updated by Michał Kłobukowski about 4 years ago

  • Blocks Story #14393: Provide support for using controlled vocabulary/terminology service when setting properties on collections added
Actions #7

Updated by Michał Kłobukowski about 4 years ago

  • Target version set to sprint 14
Actions #8

Updated by Michał Kłobukowski about 4 years ago

1. This should be done in the deploy process all automated and it should be part of the code because these configs should be able to be replicated on install from the package. ie for customers who do their own install from packages and we don't have access to.

Actions #9

Updated by Michał Kłobukowski about 4 years ago

2. For me these are two different scenarios. The config.json configures the instance so this should be done on install. However the vocabulary.json is more dynamic and it needs to be possible to change it between Installations.
In our case the vocabulary.json is generated every couple of hours from an API and replaces the previous one
In a way the vocabulary.json is like an external API itself. One possible way could be to configure the URL of the vocabulary.json in the config.json which would allow us to use a rest API directly instead of a static json file

Actions #10

Updated by Tom Clegg about 4 years ago

configure the URL of the vocabulary.json in the config.json

This sounds like the way to go. It might be a local path, or any URL that allows cross-origin requests.

We might also want to provide an example file "example-vocabulary.json" in the workbench package, and refer to that in the example config comments/documentation.

Actions #11

Updated by Chrystian Klingenberg about 4 years ago

  • Target version deleted (sprint 14)
  • Release set to 20
Actions #12

Updated by Chrystian Klingenberg over 3 years ago

  • Release changed from 20 to 19
Actions #13

Updated by Chrystian Klingenberg over 3 years ago

  • Status changed from New to Closed
Actions #14

Updated by Chrystian Klingenberg over 3 years ago

  • Target version set to Workbench2 Q3, Q4
Actions

Also available in: Atom PDF