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

refactor: use optional in variable block_device_mappings #2664

Merged
merged 1 commit into from
Nov 17, 2022

Conversation

jpalomaki
Copy link
Contributor

Should make usage a little more straightforward when one only wants to override some attributes, e.g volume size

@jpalomaki jpalomaki changed the title Use optional in variable block_device_mappings refactor: use optional in variable block_device_mappings Nov 15, 2022
modules/runners/variables.tf Show resolved Hide resolved
@npalm
Copy link
Member

npalm commented Nov 16, 2022

Please can you rebase the PR, or maybe easier re-created. I rebased earlier today next with develop. (sorry) / thanks any ways!

@jpalomaki jpalomaki reopened this Nov 17, 2022
@jpalomaki
Copy link
Contributor Author

jpalomaki commented Nov 17, 2022

@npalm PR recreated in-place. Untested atm though.

@npalm npalm merged this pull request into philips-labs:next Nov 17, 2022
npalm pushed a commit that referenced this pull request Nov 17, 2022
refactor: use optiona for variable block_device_mappings
npalm pushed a commit that referenced this pull request Dec 13, 2022
refactor: use optiona for variable block_device_mappings
npalm pushed a commit that referenced this pull request Dec 13, 2022
refactor: use optiona for variable block_device_mappings
npalm pushed a commit that referenced this pull request Dec 28, 2022
refactor: use optiona for variable block_device_mappings
npalm pushed a commit that referenced this pull request Dec 28, 2022
refactor: use optiona for variable block_device_mappings
npalm pushed a commit that referenced this pull request Dec 28, 2022
refactor: use optiona for variable block_device_mappings
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants