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

Fix default in tfe_workspace documentation #627

Merged
merged 2 commits into from
Sep 16, 2022
Merged

Conversation

gtownend
Copy link
Contributor

Description

Current documentation states that the default for file_triggers_enabled is false when the actual default is true

External links

Default value in code

@hashicorp-cla
Copy link

hashicorp-cla commented Sep 16, 2022

CLA assistant check
All committers have signed the CLA.

@gtownend gtownend marked this pull request as ready for review September 16, 2022 16:14
@gtownend gtownend requested a review from a team as a code owner September 16, 2022 16:14
Copy link
Collaborator

@brandonc brandonc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you very much for correcting this! The default was changed in 0.32.0 but the argument docs were not changed.

@brandonc brandonc merged commit 2a1b060 into hashicorp:main Sep 16, 2022
@philomory
Copy link

philomory commented Oct 3, 2022

@brandonc As I understand it, in 0.32.0 the default was supposed to be changed to false (it was true previously), but the change was made incorrectly and so nothing was actually changed. You can see that the documentation was updated in #510, it was just updated under the assumption that the intended change to the default value was actually going to take effect.

This gets even more confusing because it was stated in #510 (and the release notes for 0.32.0) that the change to the default was intended to bring the default value into line with the default value of the corresponding attribute in TFC's API, but the API Documentation linked from the release notes clearly shows that the default value of data.attributes.file-triggers-enabled is true.

I know that changing the release notes of an already-released version after-the-fact is generally frowned upon, but you may wish to consider removing this from the release notes of version 0.32.0, because announcing a breaking change that never happens is pretty awkward as well:

r/tfe_workspace: Default value of the file_triggers_enabled field is changed to false. This will align the
file_triggers_enabled field default value with the default value for the same field in the
TFC API.
If the value of the file_triggers_enabled field was not explicitly set and either of the fields working_directory
(not an empty string) or trigger_prefixes was used - to keep the behavior unchanged, the file_trigger_enabled
field should now explicitly be set to true. (#510)

I don't know if @matejrisek, @omarismail, or @sebasslash want to weigh in on this? It's pretty confusing, I lost quite a bit of time today trying to work out what was going on.

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.

4 participants