fix: Update catalog-info.yaml (#2)

update owner to spaceball

Author: tfhartmann

.editorconfig

@@ -0,0 +1,22 @@
+# http://editorconfig.org
+
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+indent_size = 4
+indent_style = space
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.{diff,patch}]
+trim_trailing_whitespace = false
+
+[*.{json,yaml,yml}]
+indent_size = 2
+indent_style = space
+
+[*.{hcl,tf,tfvars}]
+indent_size = 2
+indent_style = space

.github/CODEOWNERS

@@ -6,7 +6,7 @@
 # @global-owner1 and @global-owner2 will be requested for
 # review when someone opens a pull request.
 #*       @global-owner1 @global-owner2
-*       @broadinstitute/5cc-cga
+*       @broadinstitute/devnull @broadinstitute/spaceballs
 
 # Order is important; the last matching pattern takes the most
 # precedence. When someone opens a pull request that only

.github/dependabot.yaml

@@ -0,0 +1,12 @@
+---
+version: 2
+updates:
+  - package-ecosystem: github-actions
+    directory: /
+    groups:
+      actions:
+        patterns:
+          - "*"
+    schedule:
+      # Check for updates to GitHub Actions every month
+      interval: monthly

.github/dependabot.yml

@@ -1,18 +1,19 @@
----
-## Write Good Commit Messages
+# Write Good Commit Messages
 
 [The seven rules of a great Git commit message](https://cbea.ms/git-commit/)
 
-* Separate subject from body with a blank line
-* Limit the subject line to 50 characters
-* Capitalize the subject line
-* Do not end the subject line with a period
-* Use the imperative mood in the subject line
-* Wrap the body at 72 characters
-* Use the body to explain what and why vs. how
+- Separate subject from body with a blank line
+- Limit the subject line to 50 characters
+- Capitalize the subject line
+- Do not end the subject line with a period
+- Use the imperative mood in the subject line
+- Wrap the body at 72 characters
+- Use the body to explain what and why vs. how
 
 ## Update Providers
-When updating a provider, run the following command to update the lock file. This will ensure that the provider is available for all platforms.
+
+When updating a provider, run the following command to update the lock file.
+This will ensure that the provider is available for all platforms.
 
 ```Shell
 terraform providers lock \
@@ -24,7 +25,10 @@ terraform providers lock \
 ```
 
 ## Update Docs
-When updating docs, run the following command in the directory you want to update (dev/prod). This will ensure that the docs are available for all platforms.
+
+When updating docs, run the following command in the directory you want to
+update (dev/prod). This will ensure that the docs are available for all
+platforms.
 
 ```Shell
 docker run --rm --volume "$(pwd):/terraform-docs" -u $(id -u) quay.io/terraform-docs/terraform-docs:latest --output-file README.md --output-mode inject /terraform-docs

.github/pull_request_template.md

@@ -1,10 +1,10 @@
 ---
-name: 'checks'
+name: checks
 
-'on':
+"on":
   pull_request:
     branches:
-      - 'main'
+      - main
 
 jobs:
   conventional-commits:

.github/workflows/checks.yaml

@@ -1,9 +1,9 @@
 ---
-name: 'Close stale issues and PRs'
+name: Close stale issues and PRs
 
-'on':
+"on":
   schedule:
-    - cron: '30 1 * * *'
+    - cron: "30 1 * * *"
 
 jobs:
   stale:

.github/workflows/close-stale.yaml

@@ -0,0 +1,4 @@
+{
+  "proseWrap": "always",
+  "trailingComma": "es5"
+}

.prettierrc

@@ -1,19 +1,20 @@
+---
 apiVersion: backstage.io/v1alpha1
 kind: Component
 metadata:
-  name: kubernetes-netbox
+  annotations:
+    backstage.io/kubernetes-id: kubernetes-netbox
+    backstage.io/source-template: template:default/create-repo
+    backstage.io/techdocs-ref: dir:.
+    github.com/project-slug: broadinstitute/kubernetes-netbox
   description: netbox
+  name: kubernetes-netbox
   tags:
     - gcp
     - networking
-  annotations:
-    github.com/project-slug: broadinstitute/kubernetes-netbox
-    backstage.io/source-template: template:default/create-repo
-    backstage.io/techdocs-ref: dir:.
-    backstage.io/kubernetes-id: kubernetes-netbox
 spec:
-  type: website
+  domain: infrastructure-tools
   lifecycle: production
-  owner: 5cc-cga
+  owner: spaceballs
   system: kubernetes
-  domain: infrastructure-tools
+  type: website

catalog-info.yaml

@@ -1,29 +1,32 @@
 ## kubernetes-netbox
 
-
-
 ## Getting started
 
-Start write your documentation by adding more markdown (.md) files to this folder (/docs) or replace the content in this file.
-For more info visit [TechDoc](https://backstage.io/docs/features/techdocs/) and [TechDocs at Broad](https://backstage.broadinstitute.org/catalog/default/component/backstage/docs/techdocs/)
+Start write your documentation by adding more markdown (.md) files to this
+folder (/docs) or replace the content in this file. For more info visit
+[TechDoc](https://backstage.io/docs/features/techdocs/) and
+[TechDocs at Broad](https://backstage.broadinstitute.org/catalog/default/component/backstage/docs/techdocs/)
 
 ## Table of Contents
 
-The Table of Contents on the right is generated automatically based on the hierarchy
-of headings. Only use one H1 (`#` in Markdown) per file.
+The Table of Contents on the right is generated automatically based on the
+hierarchy of headings. Only use one H1 (`#` in Markdown) per file.
 
 ## Site navigation
 
-For new pages to appear in the left hand navigation you need edit the `mkdocs.yml`
-file in root of your repo. The navigation can also link out to other sites.
+For new pages to appear in the left hand navigation you need edit the
+`mkdocs.yml` file in root of your repo. The navigation can also link out to
+other sites.
 
-Alternatively, if there is no `nav` section in `mkdocs.yml`, a navigation section
-will be created for you. However, you will not be able to use alternate titles for
-pages, or include links to other sites.
+Alternatively, if there is no `nav` section in `mkdocs.yml`, a navigation
+section will be created for you. However, you will not be able to use alternate
+titles for pages, or include links to other sites.
 
-Note that MkDocs uses `mkdocs.yml`, not `mkdocs.yaml`, although both appear to work.
-See also <https://www.mkdocs.org/user-guide/configuration/>.
+Note that MkDocs uses `mkdocs.yml`, not `mkdocs.yaml`, although both appear to
+work. See also <https://www.mkdocs.org/user-guide/configuration/>.
 
 ## Support
 
-That's it. If you need support, reach out in [#docs-like-code](https://discord.com/channels/687207715902193673/714754240933003266) on Discord.
+That's it. If you need support, reach out in
+[#docs-like-code](https://discord.com/channels/687207715902193673/714754240933003266)
+on Discord.