Skip to content

Commit

Permalink
docs: update enterprise access token note
Browse files Browse the repository at this point in the history
  • Loading branch information
SignalRichard committed Jan 9, 2025
1 parent 8e86b50 commit f2a0e03
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -80,15 +80,15 @@ API applications can be generated for users or administrators can create "servic

Once the API application has been registered, users should reference their site's documentation at `https://[your_site]/api/docs/authentication` for details on create an access key. Users should follow the instructions for "Desktop Applications" that uses the implicit OAuth 2.0 flow to generate an `access_token`.

> Note: The user that creates the access token will be the user referenced when creating articles, questions, and answers. You may wish to use another non-user account to differentiate content generated by Terraform.
> Note: The user that creates the access token will be the user referenced when creating articles, questions, and answers even if the API application is registered to the Community user. You may wish to use another non-user account to differentiate content generated by Terraform.
## Migrating from versions < 1.x

Versions prior to 1.x are not considered stable and many changes have been made that will require manual interview to ensure that your upgrade is successful.
The following is a list of features that have been removed in version 1.x:

* `stackoverflow_filter` - This data/resource is no longer available in versions > 1.x because it is no longer needed. This resource was a direct requirement to using Stack Overflow's API v2.x and had no particular meaning besides configuring API access.
* `default_tags` - Provider default tags are no longer supported. This decision was made to simplify the code base, standardize the Terraform model state to make it reflect actual configuration code, and to promoting tags as first class resources. Tags are now available as data resources and can be used to ensure the resource dependency graph is more complete.
* `default_tags` - Provider default tags are no longer supported. This decision was made to simplify the code base, standardize the Terraform model state to make it reflect actual configuration code, and to promote tags as first class resources. Tags are now available as data resources and can be used to ensure the resource dependency graph is more complete.
* `team_name` - Provider team name field is no longer supported which simplifies the provider configuration to be able to support both Stack Overflow for Teams Business and Stack Overflow Enterprise tiers. Users should provide the `base_url` field and include the team name if applicable in the value.

The migration steps should be as follows:
Expand Down

0 comments on commit f2a0e03

Please sign in to comment.