Skip to content
New issue

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

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

Already on GitHub? # to your account

Add source_path to vagrant-cloud post-processor #5782

Closed
genebean opened this issue Jan 10, 2018 · 3 comments
Closed

Add source_path to vagrant-cloud post-processor #5782

genebean opened this issue Jan 10, 2018 · 3 comments
Labels
enhancement post-processor/vagrant-cloud wontfix Out of scope/alignment with the project, or issue is expected, intended behavior

Comments

@genebean
Copy link

I like to build and test vagrant boxes locally before uploading them anywhere. With that in mind, I would like to have a setting like the source_path one builders have in the vagrant-cloud post-processor so that after testing I could run packer again, point it at the boxes created earlier, and have it upload them. The upload template would look something like this:

{
  "variables": {
    "box_tag": "genebean/somebox",
    "cloud_token": "{{ env `VAGRANT_CLOUD_TOKEN` }}",
    "version": "{{ env `VAGRANT_BOX_VERSION`}}"
  },
  "post-processors": [
    {
      "type": "vagrant-cloud",
      "source_path: "boxes/somebox.box",
      "keep_input_artifact": true,
      "box_tag": "{{user `box_tag`}}",
      "access_token": "{{user `cloud_token`}}",
      "version": "{{user `version`}}"
    }
  ]
}
@ndench
Copy link

ndench commented Feb 2, 2018

Even if there was a flag to skip the vagrant-cloud post-processor would solve the problem too, as detailed in #2679. That way you could skip it and test the box locally then rebuild without skipping vagrant-cloud. Only problem is it would have to rebuild the whole box which would be slow (not something I'm worried about because I get CircleCI to build and push to Vagrant Cloud when I push to the master branch).

@SwampDragons
Copy link
Contributor

I added this to the 1.3.4 milestone so that I would remember to take a look at it, but I think that I'm going to close as wontfix. My reasoning here is that if you're planning to post-process separately from the build, it's better to just use the vagrant-cloud cli for uploads.

That said, we are adding the ability to "skip" post-processors using the "-except" flag in the next release, v1.3.4, so you'll be able to use @ndench's workaround if you're really determined.

@SwampDragons SwampDragons added the wontfix Out of scope/alignment with the project, or issue is expected, intended behavior label Jan 23, 2019
@SwampDragons SwampDragons removed this from the v1.3.4 milestone Jan 23, 2019
@ghost
Copy link

ghost commented Apr 1, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 1, 2020
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
enhancement post-processor/vagrant-cloud wontfix Out of scope/alignment with the project, or issue is expected, intended behavior
Projects
None yet
Development

No branches or pull requests

4 participants