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

Restore ability to substitute additional files when running an inline script #4683

Closed
mcasperson opened this issue Jun 28, 2018 · 4 comments
Closed
Assignees
Labels
kind/bug This issue represents a verified problem we are committed to solving tag/regression This issue was addressed and shipped, but subsequently broken in another release
Milestone

Comments

@mcasperson
Copy link

When running an inline script, it was possible to perform variable substitution on additional files sent down by the action handler. This was removed with OctopusDeploy/Calamari@3e14f52#diff-49b0402d8f1e9a3587fdf993a21560d6.

@mcasperson
Copy link
Author

The ability to do variable substitution on additional files has been restored.

@mcasperson mcasperson added this to the 2018.6.9 milestone Jun 28, 2018
@mcasperson mcasperson added the tag/regression This issue was addressed and shipped, but subsequently broken in another release label Jun 28, 2018
@mcasperson
Copy link
Author

mcasperson commented Jun 28, 2018

This issue will have affected terraform steps that used variable replacement in the terraform templates or variables. The variable replacement would not have been performed.

@octoreleasebot
Copy link

Release Note: Restored ability to do variable substitution on additional files with the run-script command

@mcasperson mcasperson modified the milestones: 2018.6.9, 2018.6.10 Jul 2, 2018
@michaelnoonan michaelnoonan added kind/bug This issue represents a verified problem we are committed to solving area/execution labels Aug 24, 2018
@lock
Copy link

lock bot commented Nov 23, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 23, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug This issue represents a verified problem we are committed to solving tag/regression This issue was addressed and shipped, but subsequently broken in another release
Projects
None yet
Development

No branches or pull requests

3 participants