- Notifications
You must be signed in to change notification settings - Fork3
fix: create new template version when tfvars change#98
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
fix: create new template version when tfvars change#98
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This stack of pull requests is managed by Graphite.Learn more about stacking. Join@ethanndickson and the rest of your teammates on |
2a47980
to81449d0
CompareName string `json:"name"` | ||
ID uuid.UUID `json:"id"` | ||
Name string `json:"name"` | ||
TFVars map[string]string |
ethanndicksonSep 13, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
My understanding from testing is that adding a new field to a struct is backwards compatible (which is also whyomitempty
works) - if we read some private state from an older version of the provider the map will just be nil.
81449d0
tob704ee6
Comparebf558f5
intomainUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Closes#97.