Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dynamic ETSI manifest naming during packaging #84

Open
mpeuster opened this issue Jun 1, 2018 · 0 comments
Open

Dynamic ETSI manifest naming during packaging #84

mpeuster opened this issue Jun 1, 2018 · 0 comments
Assignees
Labels
enhancement New feature or request
Projects

Comments

@mpeuster
Copy link
Collaborator

mpeuster commented Jun 1, 2018

The first version always uses a fixed name for the ETSI manifest when a package is created.

This is still aligned to the ETSI spec but requires Entry-Manifest: etsi_manifest.mf to be present in the TOSCA.meta (which is the case in the current implementation)

We can improve this by also dynamically naming the *.mf like the main descriptor to be even more aligned.

This is not super important.

@mpeuster mpeuster added the enhancement New feature or request label Jun 1, 2018
@mpeuster mpeuster self-assigned this Jun 1, 2018
@mpeuster mpeuster added this to To do in Development via automation Jun 1, 2018
@mpeuster mpeuster moved this from To do to In progress in Development Jun 1, 2018
@mpeuster mpeuster changed the title Fix: ETSI manifest naming during packaging Dynamic ETSI manifest naming during packaging Jun 6, 2018
@mpeuster mpeuster moved this from In progress to Backlog in Development Jun 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development
  
Backlog
Development

No branches or pull requests

1 participant