[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (TOSCA-180) Support of secured repositories for artifacts
[ https://issues.oasis-open.org/browse/TOSCA-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50468#comment-50468 ] Matthew Rutkowski commented on TOSCA-180: ------------------------------------------ Matt working on this for next Working draft. > 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: Moshe Elisha > > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]