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

provider/aws docs: Mark ForceNew fields, note about description #5375

Merged
merged 1 commit into from
Feb 29, 2016

Conversation

phinze
Copy link
Contributor

@phinze phinze commented Feb 29, 2016

The description field is easy to confuse for a nice field to
add an arbitrary comment to - and it's surprising that changes to this
field force a new resource, so we add a big note about it to point users
at tags.

Also marked all the other ForceNew attributes on this resource.

The `description` field is easy to confuse for a nice field to
add an arbitrary comment to - and it's surprising that changes to this
field force a new resource, so we add a big note about it to point users
at tags.

Also marked all the other ForceNew attributes on this resource.
@stack72
Copy link
Contributor

stack72 commented Feb 29, 2016

Nice addition! I think ForceNew should really be added to all docs over time - it's very useful to know what changes do!

@phinze
Copy link
Contributor Author

phinze commented Feb 29, 2016

Totally agreed - I was actually surprised that we didn't have them in the docs - I'm so used to looking at the schema in code where it's right there. 🙈

I know @jen20 has some spikes at doc generation which would take care of this as a general problem.

phinze added a commit that referenced this pull request Feb 29, 2016
provider/aws docs: Mark ForceNew fields, note about description
@phinze phinze merged commit c47af4c into master Feb 29, 2016
@phinze phinze deleted the phinze/doc-aws-sg-forcenew branch February 29, 2016 18:38
@ghost
Copy link

ghost commented Apr 27, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants