### Description of the change
replace the netcat command with wget commands.
### Benefits
Less noise in the log(s)
### Possible drawbacks
<!-- Describe any known limitations with your change -->
No limitations. As far as I am aware.
- Fixes #
https://gitea.com/gitea/helm-actions/pulls/23#issuecomment-1027779
### Additional information
As the PR Title suggests, it replaces the netcat command to a wget command which makes the noise in the log stop.
### Checklist
- [X] Parameters are documented in the `values.yaml` and added to the `README.md` using [readme-generator-for-helm](https://github.com/bitnami-labs/readme-generator-for-helm)
- [X] Breaking changes are documented in the `README.md`
- [X] Helm templating unittests are added (required when changing anything in `templates` folder)
- [X] Bash unittests are added (required when changing anything in `scripts` folder)
- [X] All added template resources MUST render a namespace in metadata
Co-authored-by: Daan Selen <dselen@systemec.nl>
Reviewed-on: https://gitea.com/gitea/helm-actions/pulls/26
Reviewed-by: ChristopherHX <christopherhx@noreply.gitea.com>
Co-authored-by: Daan Selen <dselen@nerthus.nl>
Co-committed-by: Daan Selen <dselen@nerthus.nl>
To be discussed. In https://gitea.com/gitea/helm-actions/issues/9#issuecomment-1002191 and https://gitea.com/gitea/helm-actions/pulls/13 I described that a migration of provisioning is currently not feasible due to
- helm limitations
- You are forced to repeat a lot of stuff for the default branch
- helm-actions cannot read values of the helm-gitea chart to fix this
- No agreement about making helm-gitea a optional dependency of helm-actions can be reached at the moment
# Proposal
- Create a new repository that includes both helm-gitea **and** helm-actions
- Provisioning leaves this repository as well like it did in helm-gitea
- Create that as gitea/helm-stack or whatever name
- Provisioning code and tests moves to gitea/helm-stack
We would need help with the repository creation
Reviewed-on: https://gitea.com/gitea/helm-actions/pulls/15
Reviewed-by: DaanSelen <daanselen@noreply.gitea.com>
Co-authored-by: ChristopherHX <christopherhx@noreply.gitea.com>
Co-committed-by: ChristopherHX <christopherhx@noreply.gitea.com>
_This is the first time I ever messed with helm and is an experiment to show what prevents the tests to pass and how far it still depends on the gitea chart_
### Description of the change
- Deletes a single test that seems to depend directly on gitea
- make all tests pass
- Moves all value accesses from `actions` one level up
- Copies content of the gitea chart required by the existing test
- Reveals all dependencies that needs to be decoupled
- Fixes readme generation
- add package.json
- copy dependent readme section from helm-gitea
- Removes all dependencies
- giteaRootURL is now required to be provided
- consistency check that this value has been provided
- added test for consistency failure
- nc command no longer uses an hardcoded dns name and is checked in tests
- added test
- Copied yamllint from helm-gitea
- added pnpm lock file exclusion
- Installed pnpm in the workflow
- Updated make unittest command in CI to unittest-helm
### Benefits
The existing tests are passing
### Possible drawbacks
The provision job might still not work.
### Applicable issues
- Fixes#5
### Additional information
The following usage should now deploy
```yaml
existingSecret: "somesecret"
existingSecretKey: "key"
## Specify the root URL of the Gitea instance
giteaRootURL: "http://somedomain:3000"
```
### ⚠ BREAKING
- giteaRootURL is now required to be provided
- Moves all value accesses from `actions` one level up
- The values.yml had this change without updating tests / dev Readme
Reviewed-on: https://gitea.com/gitea/helm-actions/pulls/6
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com>
Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.com>
Reviewed-by: volker.raschek <markus.pesch@web.de>
Co-authored-by: Christopher Homberger <christopher.homberger@web.de>
Co-committed-by: Christopher Homberger <christopher.homberger@web.de>
