Hello Marek, This is a very good question. I don’t have a good answer for it, looping in Brinda that might have it.
If during the validation we’re doing in CDS for the given zip we are indeed validating proper structure such as required by TOSCA CSAR, then they shouldn’t be any issues to enable that packaging type. In the backend, the expected packaging type is configurable, so on the solution side, it shouldn’t be much to adjust. (https://github.com/onap/oom/blob/master/kubernetes/cds/charts/cds-blueprints-processor/resources/config/application.properties#L37 <https://github.com/onap/oom/blob/master/kubernetes/cds/charts/cds-blueprints-processor/resources/config/application.properties#L37>) Thanks, Alexis > On Sep 6, 2019, at 1:42 AM, Kukulski, Marek (Nokia - PL/Wroclaw) > <[email protected]> wrote: > > Hi, > > In SDC when attaching a CBA artefact to a resource only zip is allow. > CONTROLLER_BLUEPRINT_ARCHIVE: > acceptedTypes: > - zip > Controller blueprint archive structure fallow TOSCA CSAR requirements so it > make we wonder why csar is not listed in acceptedTypes. > Extension should tell about expected content of a file e.g. xlsx (which is > also zip but with predefined structure) same apply to csar. > If we fallow TOSCA CSAR requirements then why we are not using csar extension > for Controller Blueprint Archive? > > BR, > Marek Kukulski > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18844): https://lists.onap.org/g/onap-discuss/message/18844 Mute This Topic: https://lists.onap.org/mt/33162972/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
