[OASIS Issue Tracker] (TOSCA-180) FIXED - CSD03 - Support of secured repositories for artifacts

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/TOSCA-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthew Rutkowski  updated TOSCA-180:
-------------------------------------

    Summary: FIXED - CSD03 - Support of secured repositories for artifacts  (was: Support of secured repositories for artifacts)

> FIXED - CSD03 - Support of secured repositories for artifacts
> -------------------------------------------------------------
>
>                 Key: TOSCA-180
>                 URL: https://issues.oasis-open.org/browse/TOSCA-180
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: New Feature
>          Components: Profile-YAML
>            Reporter: Moshe Elisha
>            Assignee: Matthew Rutkowski 
>             Fix For: CSD03
>
>
> Currently, the DSL supports two types of artifacts locations:
> 1. In the CSAR - the artifact URI is relative to the location in the CSAR file.
> 2. In an external repository - the artifact URI is a public URL to some file server.
> The file server can require credentials that can be supplied in the URL in the format "protocol://username:password@hostname/" but because we don't have concatenation functions in the DSL, we can't use get_input and the username and password will need to be "hard-coded" inside the template.
> There is a concrete need for an external repository as the size of the deployments artifacts can sometimes reach several GBs and there is a requirement from customers that the repository should be secured.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)