-
Notifications
You must be signed in to change notification settings - Fork 10.1k
command/meta: Enable migration from PSS to a backend #37949
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
base: main
Are you sure you want to change the base?
Conversation
31808ef to
a1c9209
Compare
a1c9209 to
5e08a2d
Compare
SarahFrench
left a comment
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.
I found a couple of things that need addressing, including something I missed in a past PR review - sorry! 🙈
72bcff4 to
3dc973f
Compare
3dc973f to
bb223c7
Compare
SarahFrench
left a comment
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.
Thanks for addressing those last comments! I've left some nit comments below but I don't think they should block merging & can be addresses later if needed.
| // Unconfiguring a state store (moving from state store => backend). | ||
| func (m *Meta) stateStore_c_S(ssSMgr *clistate.LocalState, dstBackendType string, dstBackend backend.Backend, newBackendState *workdir.BackendConfigState, viewType arguments.ViewType) (backend.Backend, tfdiags.Diagnostics) { |
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.
nit: The naming of this method (following conventions in backend-related methods) indicates that there is no config via the lower-case c and there is backend state via the upper-case S. This isn't true anymore- maybe it could be renamed to stateStore_toBackend or something similar instead?
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.
yeah, that is a fair point! I can rename it.
Co-authored-by: Sarah French <15078782+SarahFrench@users.noreply.github.com>
Fixes #
Target Release
1.15.x
Rollback Plan
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
CHANGELOG entry