[full-ci] Service Accounts

[kobergj]

Introduces service-accounts

[update-docs]

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

[kobergj]

Introduces auth-service service

• Provide a README.md for that service in the root folder of that service.
  • Use CamelCase for section headers.
• For images and example files used in README.md:
  • Create a folder named md-sources on the same level where README.md is located. Put all the images and example files referenced by README.md into this folder.
  • Use absolute references like https://raw.githubusercontent.com/owncloud/ocis/master/services/<service-name>/md-sources/file to make the content accessible for both README.md and owncloud.dev
    bad <img src="https://github.com/owncloud/ocis/blob/master/services/graph/images/mermaid-graph.svg" width="500" />
    good <img src="https://raw.githubusercontent.com/owncloud/ocis/master/services/graph/images/mermaid-graph.svg" width="500" />
• If new CLI command are introduced, that command must be described in readme.md.
• If new global envvar is introduced, the name must start with OCIS_.
• Add the service to the makefile in the ocis repo root.
• Make the service startable for binary and individual startup:
  • For single binary add service to ocis/pkg/runtime
  • For individual startup add service to ocis/pkg/commands
• Add the service to .drone.star to enable CI.
• Inform doc team in an early stage to review the readme AND the environment variables created.
  • The description must reflect the behaviour AND usually has a positive code quality impact.
• Create proper description strings for envvars - see other services for examples, especially when it comes to multiple values. This must include:
  • base description, set of available values, description of each value.
• When suggestable commits are created for text changes and you agree, collect them to a batch and commit them. Do not forget to rebase locally to avoid overwriting the changes made.
• If new envvars are introduced which serve the same purpose but in multiple services, an additional envvar must be added at the beginning of the list starting with OCIS_ (global envvar).
• Ensure that a service has a debug port
• If the new service introduces a new port:
  • the port must be added to port-ranges.md and to the readme.md file.
• Make sure to have a function FullDefaultConfig() in pkg/config/defaults/defaultconfig.go of your service. It is needed to create the documentation.

[ownclouders]

E2E tests failed: https://drone.owncloud.com/owncloud/ocis/23259/91/1

💥 To see the trace, please open the link in the console ...

npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/23259/tracing/user-should-be-able-to-create-and-download-a-gdpr-export-alice-2023-6-13-01-47-40.zip

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
2 Code Smells

0.8% Coverage
10.3% Duplication

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
6 Code Smells

29.1% Coverage
17.5% Duplication

[kobergj]

Just rebased to master - no extra review needed