Skip to content

Commit 53df56c

Browse files
Initial commit
0 parents  commit 53df56c

File tree

11 files changed

+147
-0
lines changed

11 files changed

+147
-0
lines changed

.github/CODEOWNERS

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
# see https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners for more information
2+
* @Unity-Technologies/ind-proj-orca-admins
Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
#Validation script for immersive-commerce-walmart-relay
2+
#This is used to validate your catalog-info.yaml
3+
4+
name: Validate Catalog-info.yaml
5+
on:
6+
pull_request:
7+
paths:
8+
- 'catalog-info.yaml'
9+
push:
10+
paths:
11+
- 'catalog-info.yaml'
12+
branches: [main]
13+
14+
jobs:
15+
validate_catalog:
16+
runs-on: ubuntu-latest
17+
steps:
18+
- id: 'Checkout'
19+
uses: actions/checkout@v3
20+
21+
- id: 'Validate'
22+
uses: 'RoadieHQ/[email protected]'

README.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
# immersive-commerce-walmart-relay
2+
[View this project in Unity Internal Developer Portal](https://developer.portal.internal.unity.com/catalog/default/component/immersive-commerce-walmart-relay) <br/>

catalog-info.yaml

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
# For more information about the available options please visit: http://go/catalog-info (VPN required)
2+
apiVersion: backstage.io/v1alpha1
3+
kind: Component
4+
metadata:
5+
annotations:
6+
github.com/project-slug: Unity-Technologies/immersive-commerce-walmart-relay
7+
backstage.io/techdocs-ref: dir:.
8+
name: immersive-commerce-walmart-relay
9+
description: "Walmart Immersive Commerce Authentication Relay Service reference implementation for AccountLinking&Checkout"
10+
labels:
11+
costcenter: "7052"
12+
spec:
13+
type: service
14+
lifecycle: pre-production
15+
owner: Unity-Technologies/ind-proj-orca-admins

docs/design.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
# Installing [tool/service] for local development
2+
3+
## Prerequisites
4+
5+
List here anything that developers need to have installed or set up before they start installing your tool/service.
6+
7+
## Installation steps
8+
9+
Use an ordered list to tell developers what they need to do to install your tool/service.
10+
11+
1. Clone [tool/service repo](put a link here)
12+
2. Run [some command]
13+
3. Run [some other command]
14+
15+
## Checking installation
16+
17+
Describe a basic command or procedure developers can run to check that everything's installed as it should.
18+

docs/index.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
# TechDocs space for immersive-commerce-walmart-relay
2+
3+
!!! note
4+
This repo has been pre-populated by RepoDB with a skeleton to get your documentation started. More information on TechDocs used at Unity can be found [here](http://go/docs-techdocs)
5+
6+
### If you are viewing this page in Unity Internal Developer Portal
7+
8+
To update this file, see `docs/index.md` in your repo.
9+
10+
### If you are viewing this page in GitHub
11+
12+
View this documentation rendered in Unity Internal Developer Portal [here](https://developer.portal.internal.unity.com/catalog/default/component/immersive-commerce-walmart-relay/docs).

docs/installation.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
# Installing [tool/service] for local development
2+
3+
## Prerequisites
4+
5+
List here anything that developers need to have installed or set up before they start installing your tool/service.
6+
7+
## Installation steps
8+
9+
Use an ordered list to tell developers what they need to do to install your tool/service.
10+
11+
1. Clone [tool/service repo](put a link here)
12+
2. Run [some command]
13+
3. Run [some other command]
14+
15+
## Checking installation
16+
17+
Describe a basic command or procedure developers can run to check that everything's installed as it should.
18+

docs/intro.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
# Introduction to [tool/service]
2+
3+
Describe your tool or service in a couple of sentences. What does it do, in the broadest terms?
4+
5+
## How [tool/service] works
6+
7+
A bit more detail here about how your tool/service works. What technologies does it use, how do they interact?
8+
9+
> Example: [tool/service] uses [technology A] to connect [technology B] with [technology C] so that [problem tool/service solves].
10+
11+
## Intended use case
12+
13+
Describe the intended use case for your tool or service, including the user groups it's aimed at and what they want to achieve with it.
14+
15+
> Example: [tool/service] allows users to [do a cool thing they couldn't otherwise], and can be used by [user persona/role] and [other user persona/role].
16+
17+
## Support
18+
19+
Who can readers of this doc contact for more information or support? Ideally link to a Slack channel, rather than individuals.
20+

docs/runbook.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
# Runbook
2+
3+
If you want a high tier of support from SRE for your tool/service, then you'll need to provide a runbook for them. You can see their template runbook [here](https://github.com/Unity-Technologies/pre-sre-runbook-template).
4+

docs/troubleshooting.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
# Troubleshooting
2+
3+
Use this page to describe troubleshooting procedures for common problems during local development.
4+
5+
## General issues
6+
7+
List a selection of steps to take for any non-specific issues.
8+
9+
* Uninstall and reinstall
10+
* Update to the latest version
11+
12+
## [Specific error message]
13+
14+
If you have issues that always occur with a specific error message, list them on this page under a heading with the error message itself, so developers can quickly identify what steps they need to take.
15+
16+
## [Other specific error message]
17+

0 commit comments

Comments
 (0)