Skip to content

chore: Use tf plugin docs#3380

Open
stevehipwell wants to merge 1 commit intointegrations:mainfrom
stevehipwell:plugin-docs-migrate
Open

chore: Use tf plugin docs#3380
stevehipwell wants to merge 1 commit intointegrations:mainfrom
stevehipwell:plugin-docs-migrate

Conversation

@stevehipwell
Copy link
Copy Markdown
Collaborator

@stevehipwell stevehipwell commented Apr 29, 2026

Resolves #2924
Resolves #2961
Resolves #2897
Resolves #3241
Closes #2987
Closes #3199


Before the change?

  • Docs were manually written using the legacy website pattern

After the change?

  • Docs auto-generated using tfplugindocs
    • Not really
    • They're using (mostly) static templates
    • We need to migrate each doc to either use either the generic template or to use dynamic sections in their templates

Pull request checklist

  • Schema migrations have been created if needed (example)
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

  • Yes
  • No

@stevehipwell stevehipwell added this to the v6.13.0 milestone Apr 29, 2026
@stevehipwell stevehipwell requested a review from deiga April 29, 2026 14:52
@stevehipwell stevehipwell self-assigned this Apr 29, 2026
@stevehipwell stevehipwell added Type: Documentation Improvements or additions to documentation Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR labels Apr 29, 2026
@github-actions
Copy link
Copy Markdown

👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

Signed-off-by: Steve Hipwell <[email protected]>
Copy link
Copy Markdown
Collaborator

@deiga deiga left a comment

Choose a reason for hiding this comment

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

Great work!

Comment on lines +4 to +5
workflow_dispatch: # push:

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Should this just be removed?

Suggested change
workflow_dispatch: # push:
workflow_dispatch:

Comment on lines +110 to +111
GITHUB_OWNER: ${{ (matrix.mode == 'individual' && vars.GH_TEST_LOGIN) ||
(matrix.mode == 'organization' && vars.GH_TEST_ORG_NAME) || '' }}
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

This can be made slightly easier to read with case() https://docs.github.com/en/actions/reference/workflows-and-actions/expressions?versionId=free-pro-team@latest&productId=actions#case

Suggested change
GITHUB_OWNER: ${{ (matrix.mode == 'individual' && vars.GH_TEST_LOGIN) ||
(matrix.mode == 'organization' && vars.GH_TEST_ORG_NAME) || '' }}
GITHUB_OWNER: ${{ case(matrix.mode == 'individual', vars.GH_TEST_LOGIN, matrix.mode == 'organization', vars.GH_TEST_ORG_NAME, '') }}

Comment on lines +70 to +71
subject-checksums: ./dist/${{ github.event.repository.name }}_${{
fromJSON(steps.goreleaser.outputs.metadata).version }}_SHA256SUMS
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

question: Will this line break work?

Get Actions secrets of the repository environment
---

# github\_actions\_environment\_secrets
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

question: are these \_ escapes relevant? I think they are unnecessary, since not every page has those

}
```

## Argument Reference
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

issue: I see that this is a copy of the existing docs, but would it make sense to us something like .SchemaMarkdown in the template here, to get the missing arguments?

Comment thread .rumdl.toml
disable = ["MD013", "MD028"]

[per-file-ignores]
".github/pull_request_template.md" = ["MD041"]
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

suggestion: I would Ignore MD009 as well in the PR template as the empty lines are meaningful in there

Suggested change
".github/pull_request_template.md" = ["MD041"]
".github/pull_request_template.md" = ["MD041", "MD009"]

Comment on lines -21 to -35
## Example Usage Security Manager Role

```terraform
locals {
security_manager_id = one([for x in data.github_organization_roles.all_roles.roles : x.role_id if x.name == "security_manager"])
}

data "github_organization_roles" "all_roles" {}

resource "github_organization_role_team" "security_managers" {
role_id = local.security_manager_id
team_slug = "example-team"
}
```

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

question: Was this removed on purpose?

fork = true
source_owner = "some-org"
source_repo = "original-repository"
```terraform
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

issue: This seems to have been mixed up. The pages example was removed as it's deprecated

GitHub Repository Custom Property can be imported using an ID made up of a combination of the names of the organization, repository, custom property separated by a `:` character, e.g.

```
```hcl
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

AFAIK these are shell and not hcl. This seems to be misaligned in multiple pages

Suggested change
```hcl
```shell

Comment thread docs/index.md
```

- You **must** add a `required_providers` block to every module that will create resources with this provider. If you do not explicitly require `integrations/github` in a submodule, your terraform run may [break in hard-to-troubleshoot ways](https://github.com/integrations/terraform-provider-github/issues/876#issuecomment-1303790559).
- You **must*- add a `required_providers` block to every module that will create resources with this provider. If you do not explicitly require `integrations/github` in a submodule, your terraform run may [break in hard-to-troubleshoot ways](https://github.com/integrations/terraform-provider-github/issues/876#issuecomment-1303790559).
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
- You **must*- add a `required_providers` block to every module that will create resources with this provider. If you do not explicitly require `integrations/github` in a submodule, your terraform run may [break in hard-to-troubleshoot ways](https://github.com/integrations/terraform-provider-github/issues/876#issuecomment-1303790559).
- You **must** add a `required_providers` block to every module that will create resources with this provider. If you do not explicitly require `integrations/github` in a submodule, your terraform run may [break in hard-to-troubleshoot ways](https://github.com/integrations/terraform-provider-github/issues/876#issuecomment-1303790559).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Type: Documentation Improvements or additions to documentation Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR

Projects

None yet

2 participants