go/lego
go/lego
1
0
Fork 0
mirror of https://github.com/go-acme/lego.git synced 2025-04-09 17:33:53 +02:00
Code Issues Releases Activity

hyperone: Minor tweaks of documentation (#1315)

Browse Source
This commit is contained in:
Adam Dobrawy 2020-12-09 21:31:54 +01:00 committed by GitHub
parent 1e1ae7f49b
commit b87d5b1efe
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/content/dns/zz_gen_hyperone.md
View File

@ -53,13 +53,13 @@ just a passport file in `~/.h1/passport.json` location.
To use this application you have to generate passport file for `sa`:
```
h1 sa credential generate --name my-passport --sa <sa ID> --passport-output-file ~/.h1/passport.json
h1 iam project sa credential generate --name my-passport --project <project ID> --sa <sa ID> --passport-output-file ~/.h1/passport.json
```
### Required permissions
Depending of environment variables usage, the application requires different permissions:
- `dns/zone/list` if `HYPERONE_ZONE_URI` is not specified
The application requires following permissions:
- `dns/zone/list`
- `dns/zone.recordset/list`
- `dns/zone.recordset/create`
- `dns/zone.recordset/delete`
@ -67,6 +67,8 @@ Depending of environment variables usage, the application requires different per
- `dns/zone.record/list`
- `dns/zone.record/delete`
All required permissions are available via platform role `tool.lego`.
## More information

8
providers/dns/hyperone/hyperone.toml
View File

@ -19,19 +19,21 @@ just a passport file in `~/.h1/passport.json` location.
To use this application you have to generate passport file for `sa`:
```
h1 sa credential generate --name my-passport --sa <sa ID> --passport-output-file ~/.h1/passport.json
h1 iam project sa credential generate --name my-passport --project <project ID> --sa <sa ID> --passport-output-file ~/.h1/passport.json
```
### Required permissions
Depending of environment variables usage, the application requires different permissions:
- `dns/zone/list` if `HYPERONE_ZONE_URI` is not specified
The application requires following permissions:
- `dns/zone/list`
- `dns/zone.recordset/list`
- `dns/zone.recordset/create`
- `dns/zone.recordset/delete`
- `dns/zone.record/create`
- `dns/zone.record/list`
- `dns/zone.record/delete`
All required permissions are available via platform role `tool.lego`.
'''
[Configuration]