16 Commits

Author SHA1 Message Date
SpeckleDevBot 91fd356c24 updating helm chart to version 0.3.2-alpha.77 2023-02-09 16:20:26 +00:00
Iain Sproat 6bef5dc9be chore(artifacthub): adds configuration for artifacthub 2023-02-09 16:10:34 +00:00
SpeckleDevBot 44bd6f0ecc updating helm chart to version 0.3.1 2023-02-09 10:57:20 +00:00
SpeckleDevBot c3af2ccae4 updating helm chart to version 0.3.1-alpha.68 2023-02-09 10:56:39 +00:00
SpeckleDevBot 180624b5e4 updating helm chart to version 0.3.0 2023-02-09 10:39:00 +00:00
SpeckleDevBot f4feed3bae updating helm chart to version 0.2.2-alpha.61 2023-02-09 10:30:17 +00:00
SpeckleDevBot 9516f1f111 updating helm chart to version 0.2.2-alpha.56 2023-02-09 10:13:30 +00:00
SpeckleDevBot c4493b15a9 updating helm chart to version 0.2.1 2023-02-08 23:13:56 +00:00
SpeckleDevBot bf9d8bd696 updating helm chart to version 0.2.1-alpha.47 2023-02-08 23:05:51 +00:00
SpeckleDevBot ff2d1cd8a8 updating helm chart to version 0.2.0 2023-02-08 22:51:19 +00:00
SpeckleDevBot 9dbafbe1d5 updating helm chart to version 0.1.1-alpha.40 2023-02-08 22:49:09 +00:00
SpeckleDevBot a840323e25 updating helm chart to version 0.1.1-alpha.34 2023-02-08 22:06:18 +00:00
SpeckleDevBot e274b11aac updating helm chart to version 0.1.1-alpha.30 2023-02-08 20:36:15 +00:00
SpeckleDevBot 2a488dc83c updating helm chart to version 0.1.1-alpha.25 2023-02-08 19:56:30 +00:00
SpeckleDevBot e773d3f526 updating helm chart to version 0.1.1-alpha.18 2023-02-08 19:43:53 +00:00
Iain Sproat 75ae8bd6c7 Initial commit on gh-pages branch 2023-02-08 19:24:21 +00:00
45 changed files with 248 additions and 1360 deletions
-105
View File
@@ -1,105 +0,0 @@
version: 2.1
workflows:
package-helm-chart:
jobs:
- get-version:
filters:
tags: &filter-allow-all
only: /.*/
- pre-commit:
filters:
tags: *filter-allow-all
- helm-package-and-publish:
filters:
tags: *filter-allow-all
branches: &filter-only-main
only:
- main
requires:
- get-version
- pre-commit
jobs:
get-version:
docker: &docker-image
- image: cimg/base:2022.04
working_directory: &workingdir /tmp/ci
steps:
- checkout
- run: mkdir -p workspace
- run:
name: set version
command: |
echo "export VERSION=$(.circleci/get_version.sh)" >> workspace/env-vars
- run:
name: store version
command: |
cat workspace/env-vars >> $BASH_ENV
- run:
name: echo version
command: |
echo "VERSION=${VERSION}"
- persist_to_workspace:
root: workspace
paths:
- env-vars
pre-commit:
parameters:
config_file:
default: ./.pre-commit-config.yaml
description: Optional, path to pre-commit config file.
type: string
cache_prefix:
default: ''
description: |
Optional cache prefix to be used on CircleCI. Can be used for cache busting or to ensure multiple jobs use different caches.
type: string
docker:
- image: speckle/pre-commit-runner:latest
resource_class: &docker-resource-class medium
working_directory: *workingdir
steps:
- checkout
- restore_cache:
keys:
- cache-pre-commit-<<parameters.cache_prefix>>-{{ checksum "<<parameters.config_file>>" }}
- run:
name: Install pre-commit hooks
command: pre-commit install-hooks --config <<parameters.config_file>>
- save_cache:
key: cache-pre-commit-<<parameters.cache_prefix>>-{{ checksum "<<parameters.config_file>>" }}
paths:
- ~/.cache/pre-commit
- run:
name: Run pre-commit
command: pre-commit run --all-files --config <<parameters.config_file>>
- run:
command: git --no-pager diff
name: git diff
when: on_fail
helm-package-and-publish:
docker:
- image: quay.io/helmpack/chart-testing:v3.7.1-amd64
resource_class: *docker-resource-class
working_directory: *workingdir
steps:
- checkout
- add_ssh_keys:
fingerprints:
- '99:72:8a:c8:d2:8d:f5:b8:66:c0:01:12:ee:24:2b:16'
- attach_workspace:
at: /tmp/workspace
- run:
name: populate environment variables
command: |
cat /tmp/workspace/env-vars >> $BASH_ENV
- run:
name: Build and Publish
command: ./.circleci/package_and_publish_helm.sh
environment:
APP_VERSION: '3.0.441-x64'
-23
View File
@@ -1,23 +0,0 @@
#!/bin/bash
set -eo pipefail
if [[ "${CIRCLE_TAG}" =~ ^[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
echo "${CIRCLE_TAG}"
exit 0
fi
# shellcheck disable=SC2068,SC2046
LAST_RELEASE="$(git describe --always --tags $(git rev-list --tags) | grep -E '^[0-9]+\.[0-9]+\.[0-9]+$' | head -n 1)"
NEXT_RELEASE="$(echo "${LAST_RELEASE}" | awk -F. -v OFS=. '{$NF += 1 ; print}')"
if [[ "${CIRCLE_BRANCH}" == "main" ]]; then
echo "${NEXT_RELEASE}-alpha.${CIRCLE_BUILD_NUM}"
exit 0
fi
# docker has a 128 character tag limit, so ensuring the branch name will be short enough
# helm uses semver 2, only valid characters are a-zA-Z0-9 and hyphen '-'
# shellcheck disable=SC2034
BRANCH_NAME_TRUNCATED="$(echo "${CIRCLE_BRANCH}" | cut -c -50 | sed 's/[^a-zA-Z0-9.-]/-/g')"
echo "${NEXT_RELEASE}-branch.${BRANCH_NAME_TRUNCATED}.${CIRCLE_BUILD_NUM}"
exit 0
-62
View File
@@ -1,62 +0,0 @@
#!/usr/bin/env bash
set -eo pipefail
TEMP_PACKAGE_DIR="${TEMP_PACKAGE_DIR:-"/tmp/.cr-release-packages"}"
HELM_PACKAGE_BRANCH="${HELM_PACKAGE_BRANCH:-"gh-pages"}"
HELM_STABLE_BRANCH="${HELM_STABLE_BRANCH:-"main"}"
HELM_CHART_DIR_PATH="${HELM_CHART_DIR_PATH:-"charts/seq-input-gelf"}"
if [[ -z "${VERSION}" ]]; then
echo "VERSION environment variable should be set"
exit 1
fi
if [[ -z "${APP_VERSION}" ]]; then
echo "APP_VERSION environment variable should be set"
exit 1
fi
if [[ -z "${GIT_EMAIL}" ]]; then
echo "GIT_EMAIL environment variable should be set"
exit 1
fi
if [[ -z "${GIT_USERNAME}" ]]; then
echo "GIT_USERNAME environment variable should be set"
exit 1
fi
echo "🧹 cleaning temporary directory"
rm -rf "${TEMP_PACKAGE_DIR}" || true
mkdir "${TEMP_PACKAGE_DIR}"
helm version -c
echo "🏗️ building dependencies"
helm dependency build "${HELM_CHART_DIR_PATH}"
echo "🎁 packaging ${HELM_CHART_DIR_PATH} with version: ${VERSION}"
helm package "${HELM_CHART_DIR_PATH}" --dependency-update --version "${VERSION}" --app-version "${APP_VERSION}" --destination "${TEMP_PACKAGE_DIR}"
echo "⏬ checking out git branch '${HELM_PACKAGE_BRANCH}'"
git config user.email "${GIT_EMAIL}"
git config user.name "${GIT_USERNAME}"
git fetch
git switch "${HELM_PACKAGE_BRANCH}"
if [[ -n "${CIRCLE_TAG}" || "${CIRCLE_BRANCH}" == "${HELM_STABLE_BRANCH}" ]]; then
echo "🛻 copying packages to stable directory"
cp -a "${TEMP_PACKAGE_DIR}/." stable/
pushd stable
helm repo index .
popd
else
cp -a "${TEMP_PACKAGE_DIR}/." incubator/
echo "🛻 copying packages to incubator directory"
pushd incubator
helm repo index .
popd
fi
echo "⏫ adding, commiting, and pushing to git repository"
git add .
git commit -m "updating helm chart to version ${VERSION}"
git push --set-upstream origin "${HELM_PACKAGE_BRANCH}"
-76
View File
@@ -1,76 +0,0 @@
# Contributor Covenant Code of Conduct
## Our Pledge
In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to making participation in our project and
our community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, sex characteristics, gender identity and expression,
level of experience, education, socio-economic status, nationality, personal
appearance, race, religion, or sexual identity and orientation.
## Our Standards
Examples of behavior that contributes to creating a positive environment
include:
- Using welcoming and inclusive language
- Being respectful of differing viewpoints and experiences
- Gracefully accepting constructive criticism
- Focusing on what is best for the community
- Showing empathy towards other community members
Examples of unacceptable behavior by participants include:
- The use of sexualized language or imagery and unwelcome sexual attention or
advances
- Trolling, insulting/derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others' private information, such as a physical or electronic
address, without explicit permission
- Other conduct which could reasonably be considered inappropriate in a
professional setting
## Our Responsibilities
Project maintainers are responsible for clarifying the standards of acceptable
behavior and are expected to take appropriate and fair corrective action in
response to any instances of unacceptable behavior.
Project maintainers have the right and responsibility to remove, edit, or
reject comments, commits, code, wiki edits, issues, and other contributions
that are not aligned to this Code of Conduct, or to ban temporarily or
permanently any contributor for other behaviors that they deem inappropriate,
threatening, offensive, or harmful.
## Scope
This Code of Conduct applies both within project spaces and in public spaces
when an individual is representing the project or its community. Examples of
representing a project or community include using an official project e-mail
address, posting via an official social media account, or acting as an appointed
representative at an online or offline event. Representation of a project may be
further defined and clarified by project maintainers.
## Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the project team at hello@speckle.systems. All
complaints will be reviewed and investigated and will result in a response that
is deemed necessary and appropriate to the circumstances. The project team is
obligated to maintain confidentiality with regard to the reporter of an incident.
Further details of specific enforcement policies may be posted separately.
Project maintainers who do not follow or enforce the Code of Conduct in good
faith may face temporary or permanent repercussions as determined by other
members of the project's leadership.
## Attribution
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
[homepage]: https://www.contributor-covenant.org
For answers to common questions about this code of conduct, see
https://www.contributor-covenant.org/faq
-50
View File
@@ -1,50 +0,0 @@
# Speckle Contribution Guidelines
## Introduction
Thank you for reading this! Speckle's a rather wide network of parts that depend on each other, either directly, indirectly or even just cosmetically.
> **Speckle** is a quite large ecosystem of moving parts. Any changes may have unintended effects, that can cause problems quickly for many people (and processes) that rely on Speckle.
This means that what might look like a simple quick change in one repo may have a big hidden cost that propagates around other parts of the project. We're all here to help each other, and this guide is meant to help you get started and promote a framework that can untangle all these dependecies through discussion!
## Bugs & Issues 🐞
### Found a new bug?
- First step is to check whether this is a new bug! We encourage you to search through the issues of the project in question **and** associated repos!
- If you come up with nothing, **open a new issue with a clear title and description**, as much relevant information as possible: system configuration, code samples & steps to reproduce the problem.
- Can't mention this often enough: tells us how to reproduce the problem! We will ignore or flag as such issues without reproduction steps.
- Try to reference & note all potentially affected projects.
### Sending a PR for Bug Fixes
You fixed something! Great! We hope you logged it first :) Make sure though that you've covered the lateral thinking needed for a bug report, as described above, also in your implementation! If there any tests, make sure they all pass. If there are none, it means they're missing - so add them!
## New Features 🎉
The golden rule is to Discuss First!
- Before embarking on adding a new feature, suggest it first as an issue with the `enhancement` label and/or title - this will allow relevant people to pitch in
- We'll now discuss your requirements and see how and if they fit within the Speckle ecosystem.
- The last step is to actually start writing code & submit a PR so we can follow along!
- All new features should, if and where possible, come with tests. We won't merge without!
> Many clients may potentially have overlapping scopes, some features might already be in dev somewhere else, or might have been postponed to the next major release due to api instability in that area. For example, adding a delete stream button in the accounts panel in rhino: this feature was planned for speckle admin, and the whole functionality of the accounts panel in rhino is to be greatly reduced!
## Cosmetic Patches ✨
Changes that are cosmetic in nature and do not add anything substantial to the stability or functionality of Speckle **will generally not be accepted**.
Why? However trivial the changes might seem, there might be subtle reasons for the original code to be as it is. Furthermore, there are a lot of potential hidden costs (that even maintainers themselves are not aware of fully!) and they eat up review time unncessarily.
> **Examples**: modifying the colour of an UI element in one client may have a big hidden cost and need propagation in several other clients that implement a similar ui element. Changing the default port or specifiying `localhost` instead of `0.0.0.0` breaks cross-vm debugging and developing.
## Wrap up
Don't worry if you get things wrong. We all do, including project owners: this document should've been here a long time ago. There's plenty of room for discussion on our community [forum](https://discourse.speckle.works).
🙌❤️💙💚💜🙌
-113
View File
@@ -1,113 +0,0 @@
---
name: Bug report
about: Help improve Speckle!
title: ''
labels: bug
assignees: ''
---
<!---
Provide a short summary in the Title above. Examples of good Issue titles:
* "Bug: Error from server when reticulating splines"
* "Bug: Revit crashes when installing connector"
-->
## Prerequisites
<!---
Please answer the following questions before submitting an issue.
-->
- [ ] I read the [contribution guidelines](https://github.com/specklesystems/speckle-server/blob/main/CONTRIBUTING.md)
- [ ] I checked the [documentation](https://speckle.guide/) and found no answer.
- [ ] I checked [existing issues](../issues?q=is%3Aissue) and found no similar issue. <!-- If you do find an existing issue, please show your support by liking it :+1: instead of creating a new issue -->
- [ ] I checked the [community forum](https://speckle.community/) for related discussions and found no answer.
- [ ] I'm reporting the issue to the correct repository (see also [speckle-server](https://github.com/specklesystems/speckle-server), [speckle-sharp](https://github.com/specklesystems/speckle-sharp), [specklepy](https://github.com/specklesystems/specklepy), [speckle-docs](https://github.com/specklesystems/speckle-docs), and [others](https://github.com/orgs/specklesystems/repositories))
## What package are you referring to?
<!---
Is it related to the server (backend) only, or does this bug relate to the frontend, viewer, objectloader or any other package?
-->
## Describe the bug
<!---
A clear and concise description of what the bug is.
-->
## To Reproduce
<!---
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
-->
## Expected behavior
<!---
A clear and concise description of what you expected to happen.
-->
## Screenshots
<!---
If applicable, add screenshots to help explain your problem.
-->
## System Info
If applicable, please fill in the below details - they help a lot!
### Desktop (please complete the following information):
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
### Smartphone (please complete the following information):
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]
## Failure Logs
<!---
Please include any relevant log snippets or files here, or upload as a file.
If including inline, please use markdown code block syntax. https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks
For example:
```
your log output here
```
-->
## Additional context
<!---
Add any other context about the problem here.
-->
## Proposed Solution (if any)
<!---
Let us know what how you would solve this.
-->
#### Optional: Affected Projects
<!---
Does this issue propagate to other dependencies or dependents? If so, list them here with links!
-->
-71
View File
@@ -1,71 +0,0 @@
---
name: Feature request
about: Suggest an idea for Speckle!
title: ''
labels: enhancement, question
assignees: ''
---
<!---
Provide a short summary in the Title above. Examples of good Issue titles:
* "Enhancement: Connector for Minecraft"
* "Enhancement: Web viewer should support tesseracts"
-->
## Prerequisites
<!---
Please answer the following questions before submitting an issue.
-->
- [ ] I read the [contribution guidelines](https://github.com/specklesystems/speckle-server/blob/main/CONTRIBUTING.md)
- [ ] I checked the [documentation](https://speckle.guide/) and found no answer.
- [ ] I checked [existing issues](../issues?q=is%3Aissue) and found no similar issue. <!-- If you do find an existing issue, please show your support by liking it :+1: instead of creating a new issue -->
- [ ] I checked the [community forum](https://speckle.community/) for related discussions and found no answer.
- [ ] I'm requesting the feature to the correct repository (see also [speckle-server](https://github.com/specklesystems/speckle-server), [speckle-sharp](https://github.com/specklesystems/speckle-sharp), [specklepy](https://github.com/specklesystems/specklepy), [speckle-docs](https://github.com/specklesystems/speckle-docs), and [others](https://github.com/orgs/specklesystems/repositories))
## What package are you referring to?
<!---
Is it related to the server (backend) only, or does this feature request relate to the frontend, viewer, objectloader or any other package?
-->
## Is your feature request related to a problem? Please describe.
<!---
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
-->
## Describe the solution you'd like
<!---
A clear and concise description of what you want to happen.
-->
## Describe alternatives you've considered
<!---
A clear and concise description of any alternative solutions or features you've considered.
-->
## Additional context
<!---
Add any other context or screenshots about the feature request here.
Have you seen this feature implemented in any other software? Can you provide screenshots or links to video or documentation?
What works well about these existing features in other software? What doesn't work well?
-->
## Related issues or community discussions
<!---
Is this feature request related to (but sufficiently distinct from) any existing issues?
Does this feature request require other features to be available beforehand?
Has this feature been discussed in the community forum, please link here? https://speckle.community/
-->
-7
View File
@@ -1,7 +0,0 @@
---
name: Papercut
about: Small annoyances and issues that are not technically bugs
title: ''
labels: '✂️ paper-cut'
assignees: ''
---
-102
View File
@@ -1,102 +0,0 @@
<!---
Provide a short summary in the Title above. Examples of good PR titles:
* "Feature: adds metrics to component"
* "Fix: resolves duplication in comment thread"
* "Update: apollo v2.34.0"
-->
## Description & motivation
<!---
Describe your changes, and why you're making them. What benefit will this have to others?
Is this linked to an open Github issue, a thread in Speckle community,
or another pull request? Link it here.
If it is related to a Github issue, and resolves it, please link to the issue number, e.g.:
Fixes #85, Fixes #22, Fixes username/repo#123
Connects #123
-->
## Changes:
<!---
- Item 1
- Item 2
-->
## To-do before merge:
<!---
(Optional -- remove this section if not needed)
Include any notes about things that need to happen before this PR is merged, e.g.:
- [ ] Change the base branch
- [ ] Ensure PR #56 is merged
-->
## Screenshots:
<!---
Include a screenshot the before and after. This can be a screenshot of a plugin, web frontend, or output in a terminal.
-->
## Validation of changes:
<!---
Describe what tests have been added or amended, and why these demonstrate it works and will prevent this feature being accidentally broken by future changes.
-->
## Checklist:
<!---
This checklist is mostly useful as a reminder of small things that can easily be
forgotten it is meant as a helpful tool rather than hoops to jump through.
Put an `x` between the square brackets, e.g. [x], for all the items that apply,
make notes next to any that haven't been addressed, and remove any items that are not relevant to this PR.
-->
- [ ] My pull request follows the guidelines in the [Contributing guide](https://github.com/specklesystems/speckle-server/blob/main/CONTRIBUTING.md)?
- [ ] My pull request does not duplicate any other open [Pull Requests](../../pulls) for the same update/change?
- [ ] My commits are related to the pull request and do not amend unrelated code or documentation.
- [ ] My code follows a similar style to existing code.
- [ ] I have added appropriate tests.
- [ ] I have updated or added relevant documentation.
## References
<!---
(Optional -- remove this section if not needed )
Include **important** links regarding the implementation of this PR.
This usually includes a RFC or an aggregation of issues and/or individual conversations
that helped put this solution together. This helps ensure we retain and share knowledge
regarding the implementation, and may help others understand motivation and design decisions etc..
-->
-12
View File
@@ -1,12 +0,0 @@
name: Update issue Status
on:
issues:
types: [closed]
jobs:
update_issue:
uses: specklesystems/github-actions/.github/workflows/project-add-issue.yml@main
secrets: inherit
with:
issue-id: ${{ github.event.issue.node_id }}
-12
View File
@@ -1,12 +0,0 @@
name: Move new issues into Project
on:
issues:
types: [opened]
jobs:
track_issue:
uses: specklesystems/github-actions/.github/workflows/project-add-issue.yml@main
secrets: inherit
with:
issue-id: ${{ github.event.issue.node_id }}
-39
View File
@@ -1,39 +0,0 @@
repos:
- repo: https://github.com/pre-commit/mirrors-prettier
rev: 'v3.0.0-alpha.4'
hooks:
- id: prettier
- repo: https://github.com/pre-commit/pre-commit-hooks
rev: 'v4.4.0'
hooks:
- id: check-yaml
exclude: 'charts'
- id: check-merge-conflict
- id: check-executables-have-shebangs
- id: check-shebang-scripts-are-executable
- id: check-symlinks
- id: check-vcs-permalinks
- id: trailing-whitespace
- id: end-of-file-fixer
exclude: 'charts/seq-input-gelf/README.md'
- repo: https://github.com/syntaqx/git-hooks
rev: 'v0.0.17'
hooks:
- id: circleci-config-validate
- repo: https://github.com/Jarmos-san/shellcheck-precommit
rev: 'v0.2.0'
hooks:
- id: shellcheck-system
- repo: https://github.com/norwoodj/helm-docs
rev: v1.11.0
hooks:
- id: helm-docs
args:
- --chart-search-root=charts
ci:
autoupdate_schedule: weekly
-2
View File
@@ -1,2 +0,0 @@
.github
charts
-11
View File
@@ -1,11 +0,0 @@
{
"trailingComma": "none",
"tabWidth": 2,
"semi": false,
"endOfLine": "auto",
"bracketSpacing": true,
"vueIndentScriptAndStyle": false,
"htmlWhitespaceSensitivity": "ignore",
"printWidth": 88,
"singleQuote": true
}
-201
View File
@@ -1,201 +0,0 @@
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright 2020 AEC Systems
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-89
View File
@@ -1,89 +0,0 @@
# Seq Input GELF - Helm Chart
[![Twitter Follow](https://img.shields.io/twitter/follow/SpeckleSystems?style=social)](https://twitter.com/SpeckleSystems) [![Community forum users](https://img.shields.io/discourse/users?server=https%3A%2F%2Fdiscourse.speckle.works&style=flat-square&logo=discourse&logoColor=white)](https://discourse.speckle.works) [![website](https://img.shields.io/badge/https://-speckle.systems-royalblue?style=flat-square)](https://speckle.systems) [![docs](https://img.shields.io/badge/docs-speckle.guide-orange?style=flat-square&logo=read-the-docs&logoColor=white)](https://speckle.guide/dev/)
## Introduction
This repository contains a Helm Chart for deploying [DataLust's `seq-input-gelf`](https://docs.datalust.co/docs/using-gelf#enabling-gelf-in-docker) Docker image to a Kubernetes cluster.
If deploying `seq-input-gelf` alongside `seq`, please use DataLust's [official Helm Chart](https://github.com/datalust/helm.datalust.co/tree/main/charts/seq). This Helm Chart allows `seq-input-gelf` to be deployed independently of `seq`.
You may wish to deploy `seq-input-gelf` if you are exporting logs in Graylog Extended Log Format (GELF).
You may wish to deploy `seq-input-gelf` independently of `seq` if you have a multiple Kubernetes clusters, and wish to transfer log data from a source cluster to a target cluster, running `seq`. Alternatively, you may have `seq` deployed on a non-Kubernetes environment, and wish to export logs messages from Kubernetes to that external seq instance.
This project or repository is in no way affiliated with DataLust or Seq.
## Documentation
### Usage
1. You will require [Helm](https://helm.sh/docs/intro/install/) and access to a [Kubernetes](https://kubernetes.io/) cluster to which you have appropriate permissions to deploy resources.
1. Clone this repository and in a shell terminal, `cd` in to the root directory of the cloned repository.
1. Create a namespace to deploy into:
```shell
kubectl create namespace seq-input-gelf
```
1. Run the following command to create a secret containing your deployment key, replacing `YOURAPIKEY` with an [API key generated by your Seq instance](https://docs.datalust.co/docs/api-keys):
```shell
kubectl create secret generic seq-api-key --from-literal=api-key=YOURAPIKEY --namespace seq-input-gelf
```
1. Add the helm repository for this Helm Chart
```shell
helm repo add seq-input-gelf https://specklesystems.github.io/seq-input-gelf/stable
```
1. Update the value of `seq.url` in `./examples/values.yaml` file to match the url of your seq instance. The default example assumes seq is hosted within the same Kubernetes cluster with a Service named `seq` within a namespace named `seq`. Please adjust this as required.
1. Run the following command to install the helm chart in your kubernetes cluster. Note that this will create a new namespace named `seq-input-gelf`:
```shell
helm upgrade seq-input-gelf \
seq-input-gelf \
--namespace seq-input-gelf \
--install \
--values ./examples/values.yaml
```
1. Verify that the deployment has successfully [rolled out](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#deployment-status):
```shell
kubectl rollout status deployment/seq-input-gelf --namespace seq-input-gelf
```
### Developing & Debugging
1. Ensure the Helm chart can be templated:
```shell
helm template seq-input-gelf ./charts/seq-input-gelf
```
### Contributing
Please make sure you read the [contribution guidelines](.github/CONTRIBUTING.md) and [code of conduct](.github/CODE_OF_CONDUCT.md) for an overview of the practices we try to follow.
#### Prerequisites
1. Your code must pass our pre-commit checks in order to be accepted.
1. Install [pre-commit](https://pre-commit.com/#install).
1. In your shell terminal, `cd` to the root directory of this repository.
1. Run `pre-commit install`.
1. Review the output and adjust your contribution as necessary.
### Community
This Helm Chart is maintained by Speckle. The Speckle Community hangs out on [the forum](https://discourse.speckle.works), do join and introduce yourself & feel free to ask us questions!
## Security
For any security vulnerabilities or concerns, please contact us directly at security[at]speckle.systems.
## License
Unless otherwise described, the code in this repository is licensed under the Apache-2.0 License. Please note that some modules, extensions or code herein might be otherwise licensed. This is indicated either in the root of the containing folder under a different license file, or in the respective file's header. If you have any questions, don't hesitate to get in touch with us via [email](mailto:hello@speckle.systems).
-12
View File
@@ -1,12 +0,0 @@
# Security Policy
## Supported Versions
| Version | Supported |
| ------- | ------------------ |
| 2.2.+ | :white_check_mark: |
| < 2.2 | :x: |
## Reporting a Vulnerability
Hi! If you've found something off, we'd be more than happy if you would report it via security@speckle.systems. We will work together with you to correctly identify the cause and implement a fix. Thanks for helping make Speckle safer!
View File
-23
View File
@@ -1,23 +0,0 @@
# Patterns to ignore when building packages.
# This supports shell glob matching, relative path matching, and
# negation (prefixed with !). Only one pattern per line.
.DS_Store
# Common VCS dirs
.git/
.gitignore
.bzr/
.bzrignore
.hg/
.hgignore
.svn/
# Common backup files
*.swp
*.bak
*.tmp
*.orig
*~
# Various IDEs
.project
.idea/
*.tmproj
.vscode/
-13
View File
@@ -1,13 +0,0 @@
apiVersion: v2
appVersion: "3.0.441-x64"
description: A Helm chart for deploying seq-input-gelf to Kubernetes
home: 'https://speckle.systems/'
icon: 'https://speckle.xyz/logo.svg'
maintainers:
- name: Speckle Systems
url: 'https://speckle.systems/'
name: seq-input-gelf
sources:
- 'https://github.com/specklesystems/speckle-server'
type: application
version: 0.1.0
-46
View File
@@ -1,46 +0,0 @@
# seq-input-gelf
![Version: 0.1.0](https://img.shields.io/badge/Version-0.1.0-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 3.0.441-x64](https://img.shields.io/badge/AppVersion-3.0.441--x64-informational?style=flat-square)
A Helm chart for deploying seq-input-gelf to Kubernetes
**Homepage:** <https://speckle.systems/>
## Maintainers
| Name | Email | Url |
| ---- | ------ | --- |
| Speckle Systems | | <https://speckle.systems/> |
## Source Code
* <https://github.com/specklesystems/speckle-server>
## Values
| Key | Type | Default | Description |
|-----|------|---------|-------------|
| affinity | object | `{}` | |
| fullnameOverride | string | `""` | |
| image.pullPolicy | string | `"IfNotPresent"` | |
| image.repository | string | `"datalust/seq-input-gelf"` | |
| image.tag | string | `""` | |
| imagePullSecrets | list | `[]` | |
| nameOverride | string | `""` | |
| nodeSelector | object | `{}` | |
| podAnnotations | object | `{}` | |
| replicaCount | int | `1` | The number of instances of seq-input-gelf to deploy |
| resources | object | `{}` | |
| seq.apiKey.secretKey | string | `"api-key"` | The key in the Kubernetes secret containing the Seq API key |
| seq.apiKey.secretName | string | `"seq-api-key"` | The name of the Kubernetes secret containing the Seq API key |
| seq.diagnosticLogging | bool | `true` | Whether to enable diagnostic logging |
| seq.rustBackTrace | int | `0` | Whether to enable backtrace logging (used for debugging). 0 = disabled, 1 = enabled. |
| seq.url | string | `"http://seq:5341"` | The URL of the Seq server to send events to |
| service.port | int | `12201` | The port on which seq-input-gelf will listen for GELF messages |
| service.protocol | string | `"TCP"` | The protocol (either TCP or UDP) used by seq-input-gelf to listen for GELF messages |
| service.type | string | `"ClusterIP"` | |
| serviceAccount.annotations | object | `{}` | Annotations to add to the service account |
| serviceAccount.create | bool | `true` | Specifies whether a service account should be created |
| serviceAccount.name | string | `""` | The name of the service account to use. If not set and create is true, a name is generated using the fullname template |
| tolerations | list | `[]` | |
@@ -1 +0,0 @@
🎉 Thank you for deploying seq-input-gelf!
@@ -1,68 +0,0 @@
{{/*
Expand the name of the chart.
*/}}
{{- define "seq-input-gelf.name" -}}
{{- default .Chart.Name .Values.nameOverride | trunc 63 | trimSuffix "-" }}
{{- end }}
{{/*
Create a default fully qualified app name.
We truncate at 63 chars because some Kubernetes name fields are limited to this (by the DNS naming spec).
If release name contains chart name it will be used as a full name.
*/}}
{{- define "seq-input-gelf.fullname" -}}
{{- if .Values.fullnameOverride }}
{{- .Values.fullnameOverride | trunc 63 | trimSuffix "-" }}
{{- else }}
{{- $name := default .Chart.Name .Values.nameOverride }}
{{- if contains $name .Release.Name }}
{{- .Release.Name | trunc 63 | trimSuffix "-" }}
{{- else }}
{{- printf "%s-%s" .Release.Name $name | trunc 63 | trimSuffix "-" }}
{{- end }}
{{- end }}
{{- end }}
{{/*
*/}}
{{- define "seq-input-gelf.testname" -}}
{{- printf "%s-test" ( include "seq-input-gelf.fullname" . ) }}
{{- end }}
{{/*
Create chart name and version as used by the chart label.
*/}}
{{- define "seq-input-gelf.chart" -}}
{{- printf "%s-%s" .Chart.Name .Chart.Version | replace "+" "_" | trunc 63 | trimSuffix "-" }}
{{- end }}
{{/*
Common labels
*/}}
{{- define "seq-input-gelf.labels" -}}
helm.sh/chart: {{ include "seq-input-gelf.chart" . }}
{{ include "seq-input-gelf.selectorLabels" . }}
{{- if .Chart.AppVersion }}
app.kubernetes.io/version: {{ .Chart.AppVersion | quote }}
{{- end }}
app.kubernetes.io/managed-by: {{ .Release.Service }}
{{- end }}
{{/*
Selector labels
*/}}
{{- define "seq-input-gelf.selectorLabels" -}}
app.kubernetes.io/name: {{ include "seq-input-gelf.name" . }}
app.kubernetes.io/instance: {{ .Release.Name }}
{{- end }}
{{/*
Create the name of the service account to use
*/}}
{{- define "seq-input-gelf.serviceAccountName" -}}
{{- if .Values.serviceAccount.create }}
{{- default (include "seq-input-gelf.fullname" .) .Values.serviceAccount.name }}
{{- else }}
{{- default "default" .Values.serviceAccount.name }}
{{- end }}
{{- end }}
@@ -1,93 +0,0 @@
apiVersion: apps/v1
kind: Deployment
metadata:
name: {{ include "seq-input-gelf.fullname" . }}
labels:
{{- include "seq-input-gelf.labels" . | nindent 4 }}
spec:
replicas: {{ .Values.replicaCount }}
selector:
matchLabels:
{{- include "seq-input-gelf.selectorLabels" . | nindent 6 }}
template:
metadata:
{{- with .Values.podAnnotations }}
annotations:
{{- toYaml . | nindent 8 }}
{{- end }}
labels:
{{- include "seq-input-gelf.selectorLabels" . | nindent 8 }}
spec:
{{- with .Values.imagePullSecrets }}
imagePullSecrets:
{{- toYaml . | nindent 8 }}
{{- end }}
serviceAccountName: {{ include "seq-input-gelf.serviceAccountName" . }}
securityContext:
fsGroup: 2000
runAsUser: 1000
runAsGroup: 3000
runAsNonRoot: true
containers:
- name: {{ .Chart.Name }}
securityContext:
capabilities:
drop:
- ALL
readOnlyRootFilesystem: true
allowPrivilegeEscalation: false
image: "{{ .Values.image.repository }}:{{ .Values.image.tag | default .Chart.AppVersion }}"
imagePullPolicy: {{ .Values.image.pullPolicy }}
ports:
- name: gelf
containerPort: {{ .Values.service.port }}
protocol: {{ .Values.service.protocol }}
# TODO: docker image does not yet support liveness and readiness probes
# livenessProbe:
# httpGet:
# path: /
# port: http
# readinessProbe:
# httpGet:
# path: /
# port: http
resources:
{{- toYaml .Values.resources | nindent 12 }}
env:
- name: SEQ_ADDRESS
value: {{ .Values.seq.url }}
- name: SEQ_API_KEY
valueFrom:
secretKeyRef:
name: {{ .Values.seq.apiKey.secretName }}
key: {{ .Values.seq.apiKey.secretKey }}
- name: GELF_ADDRESS
value: {{ printf "%s://0.0.0.0:%d" ( lower .Values.service.protocol ) ( .Values.service.port | int ) }}
- name: GELF_ENABLE_DIAGNOSTICS
value: {{ .Values.seq.diagnosticLogging | quote }}
# TODO support mounting of certificates from secrets
# - name: GELF_CERTIFICATE_PATH
# value: /certs/seq-input-gelf.crt
# - name: GELF_CERTIFICATE_PRIVATE_KEY_PATH
# value: /certs/seq-input-gelf.key
- name: RUST_BACKTRACE
value: {{ .Values.seq.rustBackTrace | quote }}
volumeMounts:
# mount an empty dir to /tmp to prevent errors as readOnlyRootFilesystem is true
- mountPath: /tmp
name: tmp
volumes:
- name: tmp
emptyDir: {}
{{- with .Values.nodeSelector }}
nodeSelector:
{{- toYaml . | nindent 8 }}
{{- end }}
{{- with .Values.affinity }}
affinity:
{{- toYaml . | nindent 8 }}
{{- end }}
{{- with .Values.tolerations }}
tolerations:
{{- toYaml . | nindent 8 }}
{{- end }}
@@ -1,15 +0,0 @@
apiVersion: v1
kind: Service
metadata:
name: {{ include "seq-input-gelf.fullname" . }}
labels:
{{- include "seq-input-gelf.labels" . | nindent 4 }}
spec:
type: {{ .Values.service.type }}
ports:
- port: {{ .Values.service.port }}
targetPort: gelf
protocol: {{ .Values.service.protocol }}
name: gelf
selector:
{{- include "seq-input-gelf.selectorLabels" . | nindent 4 }}
@@ -1,14 +0,0 @@
{{- if .Values.serviceAccount.create -}}
apiVersion: v1
kind: ServiceAccount
metadata:
name: {{ include "seq-input-gelf.serviceAccountName" . }}
labels:
{{- include "seq-input-gelf.labels" . | nindent 4 }}
{{- with .Values.serviceAccount.annotations }}
annotations:
{{- toYaml . | nindent 4 }}
{{- end }}
secrets:
- name: {{ .Values.seq.apiKey.secretName }}
{{- end }}
@@ -1,34 +0,0 @@
kind: Job
apiVersion: batch/v1
metadata:
name: {{ include "seq-input-gelf.testname" . }}
labels:
{{- include "seq-input-gelf.labels" . | nindent 4 }}
spec:
backoffLimit: 5
activeDeadlineSeconds: 60
ttlSecondsAfterFinished: 600 #automatically deleted 10 minutes after completion
template:
metadata:
{{- with .Values.podAnnotations }}
annotations:
{{- toYaml . | nindent 8 }}
{{- end }}
spec:
securityContext:
fsGroup: 2000
runAsUser: 1000
runAsGroup: 3000
runAsNonRoot: true
containers:
- name: tcp-connection-is-alive
image: alpine
command: ["/bin/sh"]
args: ["-c", "nc -z {{ printf "%s.%s.svc.cluster.local" ( include "seq-input-gelf.fullname" . ) .Release.Namespace }} {{ .Values.service.port }}"]
securityContext:
capabilities:
drop:
- ALL
readOnlyRootFilesystem: true
allowPrivilegeEscalation: false
restartPolicy: Never
-56
View File
@@ -1,56 +0,0 @@
# -- The number of instances of seq-input-gelf to deploy
replicaCount: 1
seq:
apiKey:
# -- The name of the Kubernetes secret containing the Seq API key
secretName: seq-api-key
# -- The key in the Kubernetes secret containing the Seq API key
secretKey: api-key
# -- The URL of the Seq server to send events to
url: http://seq:5341
# -- Whether to enable diagnostic logging
diagnosticLogging: true
# -- Whether to enable backtrace logging (used for debugging). 0 = disabled, 1 = enabled.
rustBackTrace: 0
image:
repository: datalust/seq-input-gelf
pullPolicy: IfNotPresent
# Overrides the image tag whose default is the chart appVersion.
tag: ""
imagePullSecrets: []
nameOverride: ""
fullnameOverride: ""
serviceAccount:
# -- Specifies whether a service account should be created
create: true
# -- Annotations to add to the service account
annotations: {}
# -- The name of the service account to use. If not set and create is true, a name is generated using the fullname template
name: ""
podAnnotations: {}
service:
type: ClusterIP
# -- The port on which seq-input-gelf will listen for GELF messages
port: 12201
# -- The protocol (either TCP or UDP) used by seq-input-gelf to listen for GELF messages
protocol: TCP
resources: {}
# limits:
# cpu: 100m
# memory: 128Mi
# requests:
# cpu: 100m
# memory: 128Mi
nodeSelector: {}
tolerations: []
affinity: {}
-10
View File
@@ -1,10 +0,0 @@
seq:
url: http://seq.seq.svc.cluster.local:5341
resources:
limits:
cpu: 100m
memory: 128Mi
requests:
cpu: 100m
memory: 128Mi
+6
View File
@@ -0,0 +1,6 @@
repositoryID: e162dbb3-de8e-40c1-8ad6-6cc94299360a
owners:
- name: SpeckleDevops
ignore: # (optional, packages that should not be indexed by Artifact Hub)
- name: seq-input-gelf
version: alpha
+242
View File
@@ -0,0 +1,242 @@
apiVersion: v1
entries:
seq-input-gelf:
- apiVersion: v2
appVersion: 3.0.441-x64
created: "2023-02-09T16:20:25.993221494Z"
description: A Helm chart for deploying seq-input-gelf to Kubernetes
digest: 9ce195f9e4bf5daf705648ff218b134f969741ad4579a83c1bf8a7de5ddb46cb
home: https://speckle.systems/
icon: https://speckle.xyz/logo.svg
maintainers:
- name: Speckle Systems
url: https://speckle.systems/
name: seq-input-gelf
sources:
- https://github.com/specklesystems/speckle-server
type: application
urls:
- seq-input-gelf-0.3.2-alpha.77.tgz
version: 0.3.2-alpha.77
- apiVersion: v2
appVersion: 3.0.441-x64
created: "2023-02-09T16:20:25.992623056Z"
description: A Helm chart for deploying seq-input-gelf to Kubernetes
digest: 30c751c348ee2f1b9364f7dae24e68deb7c460c1ba428b4d8f5aaafcd8b129af
home: https://speckle.systems/
icon: https://speckle.xyz/logo.svg
maintainers:
- name: Speckle Systems
url: https://speckle.systems/
name: seq-input-gelf
sources:
- https://github.com/specklesystems/speckle-server
type: application
urls:
- seq-input-gelf-0.3.1.tgz
version: 0.3.1
- apiVersion: v2
appVersion: 3.0.441-x64
created: "2023-02-09T16:20:25.99217039Z"
description: A Helm chart for deploying seq-input-gelf to Kubernetes
digest: 06cbf35ac3ec20ef5b3ed84b6cae65780ccbe49879f3f47b9f99644c273fbe4d
home: https://speckle.systems/
icon: https://speckle.xyz/logo.svg
maintainers:
- name: Speckle Systems
url: https://speckle.systems/
name: seq-input-gelf
sources:
- https://github.com/specklesystems/speckle-server
type: application
urls:
- seq-input-gelf-0.3.1-alpha.68.tgz
version: 0.3.1-alpha.68
- apiVersion: v2
appVersion: 3.0.441-x64
created: "2023-02-09T16:20:25.991732264Z"
description: A Helm chart for deploying seq-input-gelf to Kubernetes
digest: dc2c6d396c2e3a7b4729cdb42840e74413448f645663d29ace4ad4659ff82089
home: https://speckle.systems/
icon: https://speckle.xyz/logo.svg
maintainers:
- name: Speckle Systems
url: https://speckle.systems/
name: seq-input-gelf
sources:
- https://github.com/specklesystems/speckle-server
type: application
urls:
- seq-input-gelf-0.3.0.tgz
version: 0.3.0
- apiVersion: v2
appVersion: 3.0.441-x64
created: "2023-02-09T16:20:25.991293082Z"
description: A Helm chart for deploying seq-input-gelf to Kubernetes
digest: 45aceaad65537e7d6baaf56cbc482354dba5083da1acab67ee260cee7b89b96f
home: https://speckle.systems/
icon: https://speckle.xyz/logo.svg
maintainers:
- name: Speckle Systems
url: https://speckle.systems/
name: seq-input-gelf
sources:
- https://github.com/specklesystems/speckle-server
type: application
urls:
- seq-input-gelf-0.2.2-alpha.61.tgz
version: 0.2.2-alpha.61
- apiVersion: v2
appVersion: 3.0.441-x64
created: "2023-02-09T16:20:25.990855972Z"
description: A Helm chart for deploying seq-input-gelf to Kubernetes
digest: 2a47a2acb52da50dccd4eb23ee010bfd983e031a984fc71d367c0af41585c453
home: https://speckle.systems/
icon: https://speckle.xyz/logo.svg
maintainers:
- name: Speckle Systems
url: https://speckle.systems/
name: seq-input-gelf
sources:
- https://github.com/specklesystems/speckle-server
type: application
urls:
- seq-input-gelf-0.2.2-alpha.56.tgz
version: 0.2.2-alpha.56
- apiVersion: v2
appVersion: 3.0.441-x64
created: "2023-02-09T16:20:25.990487017Z"
description: A Helm chart for deploying seq-input-gelf to Kubernetes
digest: 40714a2e6c9819015ae9ac8d55755e533fbd2c31f6034e7ebba54c4e2347e494
home: https://speckle.systems/
icon: https://speckle.xyz/logo.svg
maintainers:
- name: Speckle Systems
url: https://speckle.systems/
name: seq-input-gelf
sources:
- https://github.com/specklesystems/speckle-server
type: application
urls:
- seq-input-gelf-0.2.1.tgz
version: 0.2.1
- apiVersion: v2
appVersion: 3.0.441-x64
created: "2023-02-09T16:20:25.99010347Z"
description: A Helm chart for deploying seq-input-gelf to Kubernetes
digest: 60def2a4345817f32efc8c3b60437a825d938dc9876f83fafbde6b9037c2bfe2
home: https://speckle.systems/
icon: https://speckle.xyz/logo.svg
maintainers:
- name: Speckle Systems
url: https://speckle.systems/
name: seq-input-gelf
sources:
- https://github.com/specklesystems/speckle-server
type: application
urls:
- seq-input-gelf-0.2.1-alpha.47.tgz
version: 0.2.1-alpha.47
- apiVersion: v2
appVersion: 3.0.441-x64
created: "2023-02-09T16:20:25.989694672Z"
description: A Helm chart for deploying seq-input-gelf to Kubernetes
digest: c195ddf4043efee9920a688d53754064b031c431f0693a3fd859a711006b3771
home: https://speckle.systems/
icon: https://speckle.xyz/logo.svg
maintainers:
- name: Speckle Systems
url: https://speckle.systems/
name: seq-input-gelf
sources:
- https://github.com/specklesystems/speckle-server
type: application
urls:
- seq-input-gelf-0.2.0.tgz
version: 0.2.0
- apiVersion: v2
appVersion: 3.0.441-x64
created: "2023-02-09T16:20:25.989295468Z"
description: A Helm chart for deploying seq-input-gelf to Kubernetes
digest: bbcd2a9a3ed69d13ee39e2982ae327c0ca5a376f3e137752b968fb557922878b
home: https://speckle.systems/
icon: https://speckle.xyz/logo.svg
maintainers:
- name: Speckle Systems
url: https://speckle.systems/
name: seq-input-gelf
sources:
- https://github.com/specklesystems/speckle-server
type: application
urls:
- seq-input-gelf-0.1.1-alpha.40.tgz
version: 0.1.1-alpha.40
- apiVersion: v2
appVersion: 3.0.441-x64
created: "2023-02-09T16:20:25.988839522Z"
description: A Helm chart for deploying seq-input-gelf to Kubernetes
digest: 1723f3820c9f0be3248d68e1513890f3ea2260230361ed82358d69ae3c2947b0
home: https://speckle.systems/
icon: https://speckle.xyz/logo.svg
maintainers:
- name: Speckle Systems
url: https://speckle.systems/
name: seq-input-gelf
sources:
- https://github.com/specklesystems/speckle-server
type: application
urls:
- seq-input-gelf-0.1.1-alpha.34.tgz
version: 0.1.1-alpha.34
- apiVersion: v2
appVersion: 3.0.441-x64
created: "2023-02-09T16:20:25.988440131Z"
description: A Helm chart for deploying seq-input-gelf to Kubernetes
digest: 6e7e04bd3bc8da89d43228c23c8c893379aea8468d9f54ba25a0102504579843
home: https://speckle.systems/
icon: https://speckle.xyz/logo.svg
maintainers:
- name: Speckle Systems
url: https://speckle.systems/
name: seq-input-gelf
sources:
- https://github.com/specklesystems/speckle-server
type: application
urls:
- seq-input-gelf-0.1.1-alpha.30.tgz
version: 0.1.1-alpha.30
- apiVersion: v2
appVersion: 3.0.441-x64
created: "2023-02-09T16:20:25.988060051Z"
description: A Helm chart for deploying seq-input-gelf to Kubernetes
digest: a501a76dc1435851b2e3c33c90c034b0e95e1c0778e1b452d302e32e080ad9de
home: https://speckle.systems/
icon: https://speckle.xyz/logo.svg
maintainers:
- name: Speckle Systems
url: https://speckle.systems/
name: seq-input-gelf
sources:
- https://github.com/specklesystems/speckle-server
type: application
urls:
- seq-input-gelf-0.1.1-alpha.25.tgz
version: 0.1.1-alpha.25
- apiVersion: v2
appVersion: 3.0.441-x64
created: "2023-02-09T16:20:25.987667692Z"
description: A Helm chart for deploying seq-input-gelf to Kubernetes
digest: d012f9b5c8a276fe62a5de80955a3bd70184598b7308eb23c9f995c36d58eb50
home: https://speckle.systems/
icon: https://speckle.xyz/logo.svg
maintainers:
- name: Speckle Systems
url: https://speckle.systems/
name: seq-input-gelf
sources:
- https://github.com/specklesystems/speckle-server
type: application
urls:
- seq-input-gelf-0.1.1-alpha.18.tgz
version: 0.1.1-alpha.18
generated: "2023-02-09T16:20:25.987079247Z"
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.