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

Workspace options does not override custom and global module config #155

Open
avozicov opened this issue Mar 5, 2018 · 0 comments
Open
Assignees
Labels

Comments

@avozicov
Copy link
Contributor

avozicov commented Mar 5, 2018

We should fix the behavior of overriding global and custom module options by the those defined in workspace config

For example:

  • it is expected for plan option to be applied if it defined in config as follows:
[your_module_name]:
  root: './[your_module_name]'
  terraform:
    version: '0.11.0'
    plan: false      - this option is expected to be overridden by `prod workspace` config
    apply: false 
    destroy: false
    current-workspace: default
    available-workspaces:
      prod:
        plan: true    - this option should override the custom module config
        apply: false
        destroy: false
        var-files:
          - terraform.tfvars

Actual Result:

  • If we use the provided .recink.yml example the plan option is being skipped which is not expected

Note:

  • to reproduce the issue run recink run terraform with --tf-workspace='[your_workspace_env]'

Please refer to attachment for more details:
plan skipped.png

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants