-
Notifications
You must be signed in to change notification settings - Fork 3
feat: add use_classic_parameter_flow
to coderd_template
resource
#251
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
// TODO(ethanndickson): Remove this once the provider requires a Coder | ||
// deployment running `v2.15.0` or later. | ||
if newState.MaxPortShareLevel.IsUnknown() { | ||
newState.MaxPortShareLevel = curState.MaxPortShareLevel | ||
} |
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 this because I realised I could use planmodifier UseStateForUnknown
for it.
// TODO: Remove this update call (and the attribute) once the provider | ||
// requires a Coder version where this flag has been 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.
Coder 2.24 does not include the bool on CreateTemplateRequest
, only on UpdateTemplateMeta
. 2.25 does include it on CreateTemplateRequest
, however.
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.
one small clerical suggestion, but the code looks great!
Merge activity
|
Closes #240.
By popular demand, this exposes the fallback to classic parameters via the Template resource.