-
Notifications
You must be signed in to change notification settings - Fork 881
fix: persist terraform modules during template import #17665
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
Conversation
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.
removed
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.
@spikecurtis is adding a new field to the proto struct backwards compatible like in json
? Meaning, does the new field default to nil
?
I will ✔️ once I know it's backwards compatible 👍
Yes, it's back compatible at the proto layer, so only a minor version bump, assuming the server side will tolerate it being unset. Can't recall whether |
6b08bb0
to
51cebae
Compare
We need to save the source code of the terraform modules at import, so that they're available for evaluation with dynamic parameters.
The provisioner downloads the modules during the plan, which means we can have it create a tar file, send it to the backend, and then we can persist it in the database for later use.