[OASIS Issue Tracker] (TOSCA-180) 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:comment-tabpanel&focusedCommentId=50346#comment-50346 ] 

Matthew Rutkowski  commented on TOSCA-180:
------------------------------------------

Where repos would look something like this:

repositories:
  my_repo1:
    type: tosca.repositories.ObjectStorage
	  properties:
	    url: { get_input: url_1 }
		auth_token: { get_input: my_key }
		container: { get_input: bucket_name } # bucket
        artifacts:
            tomcat_tar_gz
		
  my_repo2:
    type: tosca.repositories.HttpFileServer
	  properties:
	    url: { get_input: url_2 }
	    auth_token: { get_input: username_password } # username:password
       artifacts:
          mysql_installation: files/mysql.rpm

> 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)